linux-kernel - Re: [GIT PULL] execve updates for v6.12-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wg==rBvM9G4kkT3q5GQN2Pq3M7Vyu1VG+QS7XWmpshGYw@mail.gmail.com>
Date: Thu, 26 Sep 2024 12:17:58 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Vegard Nossum <vegard.nossum@...cle.com>, Kees Cook <kees@...nel.org>, 
	linux-kernel@...r.kernel.org, Allen Pais <apais@...ux.microsoft.com>, 
	Brian Mak <makb@...iper.net>, Jeff Xu <jeffxu@...omium.org>, 
	Roman Kisel <romank@...ux.microsoft.com>, regressions@...ts.linux.dev
Subject: Re: [GIT PULL] execve updates for v6.12-rc1

On Thu, 26 Sept 2024 at 12:10, Eric W. Biederman <ebiederm@...ssion.com> wrote:
>
> One of the common causes for coredump truncation is weird interactions
> between io_uring and the coredump code.  (AKA kernel bugs).
>
> That is something you can't ask your debugger to tell you.
>
> So from 10,000 feet I think the idea is sane.

What? No. Adding printk's to chase kernel bugs is certainly a
time-honored tradition. But we don't leave them in the kernel sources
for posterity.

And none of the coredumpo failure reports had anything to do with
io_uring bugs anyway. They were literally "print out when disk filled
up or core dumps weren't enabled".

If you didn't get a core dump because the kernel didn't have core
dumps configured, we shouldn't print out some babying kernel message
about that.

None of this has anything to do with io_uring or kernel bugs.

                  Linus