All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: [CFT][PATCH] exit/bdflush: Remove the deprecated bdflush system call
@ 2021-06-29 21:55 kernel test robot
  0 siblings, 0 replies; 8+ messages in thread
From: kernel test robot @ 2021-06-29 21:55 UTC (permalink / raw)
  To: kbuild

[-- Attachment #1: Type: text/plain, Size: 2220 bytes --]

CC: kbuild-all(a)lists.01.org
In-Reply-To: <87sg10quue.fsf_-_@disp2133>
References: <87sg10quue.fsf_-_@disp2133>
TO: "Eric W. Biederman" <ebiederm@xmission.com>
TO: Michael Schmitz <schmitzmic@gmail.com>
CC: Geert Uytterhoeven <geert@linux-m68k.org>
CC: Al Viro <viro@zeniv.linux.org.uk>
CC: "linux-arch" <linux-arch@vger.kernel.org>
CC: Jens Axboe <axboe@kernel.dk>
CC: Oleg Nesterov <oleg@redhat.com>
CC: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
CC: Richard Henderson <rth@twiddle.net>
CC: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
CC: Matt Turner <mattst88@gmail.com>

Hi "Eric,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on tip/perf/core]
[also build test WARNING on arm64/for-next/core m68k/for-next hp-parisc/for-next powerpc/next s390/features tip/x86/asm linus/master sparc/master v5.13 next-20210629]
[cannot apply to sparc-next/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Eric-W-Biederman/exit-bdflush-Remove-the-deprecated-bdflush-system-call/20210630-042915
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 012669c740e6e2afa8bdb95394d06676f933dd2d
:::::: branch date: 86 minutes ago
:::::: commit date: 86 minutes ago
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
cd tools/perf && ./check-headers.sh

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


perfheadercheck warnings: (new ones prefixed by >>)
>> Warning: Kernel ABI header at 'tools/perf/arch/s390/entry/syscalls/syscall.tbl' differs from latest version at 'arch/s390/kernel/syscalls/syscall.tbl':  125< 134  common	bdflush			-				-
>> Warning: Kernel ABI header at 'tools/perf/arch/s390/entry/syscalls/syscall.tbl' differs from latest version at 'arch/s390/kernel/syscalls/syscall.tbl':  125> 134  common	bdflush			sys_ni_syscall			sys_ni_syscall

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads
@ 2021-06-21 13:54 Al Viro
  2021-06-21 18:59 ` Al Viro
  0 siblings, 1 reply; 8+ messages in thread
From: Al Viro @ 2021-06-21 13:54 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Eric W. Biederman, Michael Schmitz, linux-arch, Jens Axboe,
	Oleg Nesterov, Linux Kernel Mailing List, Richard Henderson,
	Ivan Kokshaysky, Matt Turner, alpha, Geert Uytterhoeven,
	linux-m68k, Arnd Bergmann, Ley Foon Tan, Tejun Heo, Kees Cook

On Tue, Jun 15, 2021 at 02:58:12PM -0700, Linus Torvalds wrote:

> And I think our horrible "kernel threads return to user space when
> done" is absolutely horrifically nasty. Maybe of the clever sort, but
> mostly of the historical horror sort.

How would you prefer to handle that, then?  Separate magical path from
kernel_execve() to switch to userland?  We used to have something of
that sort, and that had been a real horror...

As it is, it's "kernel thread is spawned at the point similar to
ret_from_fork(), runs the payload (which almost never returns) and
then proceeds out to userland, same way fork(2) would've done."
That way kernel_execve() doesn't have to do anything magical.

Al, digging through the old notes and current call graph...

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2021-06-30 12:56 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-29 21:55 [CFT][PATCH] exit/bdflush: Remove the deprecated bdflush system call kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2021-06-21 13:54 Kernel stack read with PTRACE_EVENT_EXIT and io_uring threads Al Viro
2021-06-21 18:59 ` Al Viro
2021-06-21 19:22   ` Linus Torvalds
2021-06-21 20:03     ` Eric W. Biederman
2021-06-21 23:15       ` Linus Torvalds
2021-06-22 20:52         ` Eric W. Biederman
2021-06-23  0:41           ` Linus Torvalds
2021-06-23 14:33             ` Eric W. Biederman
2021-06-24 18:57               ` [PATCH 0/9] Refactoring exit Eric W. Biederman
2021-06-24 22:45                 ` Al Viro
2021-06-27 22:13                   ` Al Viro
2021-06-27 22:59                     ` Michael Schmitz
2021-06-28  7:31                       ` Geert Uytterhoeven
2021-06-28 17:14                         ` Michael Schmitz
2021-06-28 19:17                           ` Geert Uytterhoeven
2021-06-28 20:13                             ` Michael Schmitz
2021-06-28 21:18                               ` Geert Uytterhoeven
2021-06-28 23:42                                 ` Michael Schmitz
2021-06-29 20:28                                   ` [CFT][PATCH] exit/bdflush: Remove the deprecated bdflush system call Eric W. Biederman
2021-06-29 20:28                                     ` Eric W. Biederman
2021-06-29 21:45                                     ` Michael Schmitz
2021-06-29 21:45                                       ` Michael Schmitz
2021-06-30  8:24                                     ` Geert Uytterhoeven
2021-06-30  8:37                                     ` Arnd Bergmann
2021-06-30 12:30                                     ` Cyril Hrubis

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.