Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>, "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
Subject: Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
From: Michael Schmitz <schmitzmic@xxxxxxxxx>
Date: Thu, 17 Jun 2021 07:40:57 +1200
Cc: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, linux-arch <linux-arch@xxxxxxxxxxxxxxx>, Jens Axboe <axboe@xxxxxxxxx>, Oleg Nesterov <oleg@xxxxxxxxxx>, Al Viro <viro@xxxxxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Richard Henderson <rth@xxxxxxxxxxx>, Ivan Kokshaysky <ink@xxxxxxxxxxxxxxxxxxxx>, Matt Turner <mattst88@xxxxxxxxx>, alpha <linux-alpha@xxxxxxxxxxxxxxx>, linux-m68k <linux-m68k@xxxxxxxxxxxxxxx>, Arnd Bergmann <arnd@xxxxxxxxxx>, Ley Foon Tan <ley.foon.tan@xxxxxxxxx>, Tejun Heo <tj@xxxxxxxxxx>, Kees Cook <keescook@xxxxxxxxxxxx>
In-reply-to: <CAMuHMdUkhbq+tOyrpyd5hKGGcpYduBnbnXKFBwEfCGjw5XGYVA@mail.gmail.com>
References: <87sg1p30a1.fsf@disp2133> <CAHk-=wjiBXCZBxLiCG5hxpd0vMkMjiocenponWygG5SCG6DXNw@mail.gmail.com> <87pmwsytb3.fsf@disp2133> <CAHk-=wgdO5VwSUFjfF9g=DAQNYmVxzTq73NtdisYErzdZKqDGg@mail.gmail.com> <87sg1lwhvm.fsf@disp2133> <CAHk-=wgsnMTr0V-0F4FOk30Q1h7CeT8wLvR1MSnjack7EpyWtQ@mail.gmail.com> <6e47eff8-d0a4-8390-1222-e975bfbf3a65@gmail.com> <924ec53c-2fd9-2e1c-bbb1-3fda49809be4@gmail.com> <87eed4v2dc.fsf@disp2133> <5929e116-fa61-b211-342a-c706dcb834ca@gmail.com> <87fsxjorgs.fsf@disp2133> <CAMuHMdUkhbq+tOyrpyd5hKGGcpYduBnbnXKFBwEfCGjw5XGYVA@mail.gmail.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1

Hi Geert,

On 16/06/21 7:38 pm, Geert Uytterhoeven wrote:

Hi Eric,

On Tue, Jun 15, 2021 at 9:32 PM Eric W. Biederman <ebiederm@xxxxxxxxxxxx> wrote:

Do you happen to know if there is userspace that will run
in qemu-system-m68k that can be used for testing?

There's a link to an image in Laurent's patch series "[PATCH 0/2]
m68k: Add Virtual M68k Machine"
https://lore.kernel.org/linux-m68k/20210323221430.3735147-1-laurent@xxxxxxxxx/


Thanks, I'll try that one.

I'll try and implement a few of the solutions Eric came up with foralpha, unless someone beats me to it (Andreas?).


Cheers,

    Michael


Gr{oetje,eeting}s,

                         Geert

References:
- Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Eric W. Biederman
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Linus Torvalds
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Eric W. Biederman
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Linus Torvalds
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Eric W. Biederman
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Linus Torvalds
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Michael Schmitz
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Michael Schmitz
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Eric W. Biederman
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Michael Schmitz
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Eric W. Biederman
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Geert Uytterhoeven

Prev by Date: [PATCH 2/2] alpha/ptrace: Add missing switch_stack frames
Next by Date: Re: [PATCH 1/2] alpha/ptrace: Record and handle the absence of switch_stack
Previous by thread: Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
Next by thread: [PATCH v2 1/2] mm: rename pud_page_vaddr to pud_pgtable and make it return pmd_t *
Index(es):
- Date
- Thread

[Index of Archives] [Netdev] [Linux Wireless] [Kernel Newbies] [Security] [Linux for Hams] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux Admin] [Samba]