From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Schmitz Subject: Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads Date: Wed, 16 Jun 2021 08:56:35 +1200 Message-ID: <7277aa4b-5d3f-6bb3-379a-470df4addd15@gmail.com> References: <87sg1p30a1.fsf@disp2133> <87pmwsytb3.fsf@disp2133> <87sg1lwhvm.fsf@disp2133> <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> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=sBxLxf4FrcsggEOYTT1dFKc27Ben3JcpMZ+iTHfSh4M=; b=qoOPzfCWsyStJrRTj3ypUmLWs9KaVh+ew/9w7Gc5TP4nnZNPghDlsVSApsafxGQD6c c7OgbmhU2BGKtsYhZ+6cXCZ0BW1t35QwpzzEVRT2Ad3RlYx/2Yot2XoaH/g1y63nbYPT 4ewM2wWuQvk81/v/Ykalqh3IJjnuFQ1CLAz2SIjIfFzrL2zxgm2/GEfNu79rIXWaYAyI IQKVYw3f+KOLPEAQj/A7RoYydAHO29/vHTCPS/LRQ+TBLs9Ve1aotzmLKJ0fBxkNxlBY V0WN6qYalvfZN980nCq5a0KEU7YQcGUNsohKLzvD7Oyek+5fOatozOwOM505e3f7R0GL 144w== In-Reply-To: <87fsxjorgs.fsf@disp2133> Content-Language: en-US List-ID: Content-Type: text/plain; charset="utf-8"; format="flowed" To: "Eric W. Biederman" Cc: Linus Torvalds , linux-arch , Jens Axboe , Oleg Nesterov , Al Viro , Linux Kernel Mailing List , Richard Henderson , Ivan Kokshaysky , Matt Turner , alpha , Geert Uytterhoeven , linux-m68k , Arnd Bergmann , Ley Foon Tan , Tejun Heo , Kees Cook , John Paul Adrian Glaubitz Hi Eric, On 16/06/21 7:30 am, Eric W. Biederman wrote: > >>> The io_uring tasks are special in that they are user process >>> threads that never run in userspace. So as long as everything >>> ptrace can read is accessible on that process all is well. >> OK, I'm testing a patch that would save extra context in sys_io_uring_setup, >> which ought to ensure that for m68k. > I had to update ret_from_kernel_thread to pop that state to get Linus's > change to boot. Apparently kernel_threads exiting needs to be handled. Hadn't yet got to that stage, sorry. Still stress testing stage 1 of my fix (push complete context). I would have thought that this should be sufficient (gives us a complete stack frame for ptrace code to work on)? But it makes sense that when you push an extra stack frame, you'd need to pop that on exit. > >>> Having stared a bit longer at the code I think the short term >>> fix for both of PTRACE_EVENT_EXIT and io_uring is to guard >>> them both with CONFIG_HAVE_ARCH_TRACEHOOK. > Which does not work because nios2 which looks susceptible > sets CONFIG_HAVE_ARCH_TRACEHOOK. > > A further look shows that there is also PTRACE_EVENT_EXEC that > needs to be handled so execve and execveat need to be wrapped > as well. > > Do you happen to know if there is userspace that will run > in qemu-system-m68k that can be used for testing? I surmise so. I don't use qemu myself - either ARAnyM, or actual hardware. Hardware is limited to 14 MB RAM, which has prevented me from using more than simple regression testing. In particular, I can't test sys_io_uring_setup there. Adrian uses qemu a lot, and has supplied disk images to work from on occasion. Maybe he's got something recent enough to support sys_io_uring_setup ... I've CC:ed him in, as I'd love to do some more testing as well. Cheers,     Michael > > Eric >