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: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
Subject: Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
Date: Wed, 16 Jun 2021 09:38:22 +0200
Cc: Michael Schmitz <schmitzmic@xxxxxxxxx>, 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: <87fsxjorgs.fsf@disp2133>
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>

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/

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Follow-Ups:
- Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
  - From: Michael Schmitz

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

Prev by Date: Re: [PATCH v2 0/3] arm64: Enable BTI for the executable as well as the interpreter
Next by Date: RE: [PATCH 1/3] riscv: optimized memcpy
Previous by thread: Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
Next by thread: Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Kernel Newbies] [x86 Platform Driver] [Netdev] [Linux Wireless] [Netfilter] [Bugtraq] [Linux Filesystems] [Yosemite Discussion] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper]