[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiJiePHNw3Whxm9n==h3-JwXojefAN3OiDzT89BO3jDew@mail.gmail.com>
Date: Thu, 26 Sep 2024 11:43:22 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Vegard Nossum <vegard.nossum@...cle.com>
Cc: Kees Cook <kees@...nel.org>, linux-kernel@...r.kernel.org,
Allen Pais <apais@...ux.microsoft.com>, Brian Mak <makb@...iper.net>,
"Eric W. Biederman" <ebiederm@...ssion.com>, 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 11:29, Vegard Nossum <vegard.nossum@...cle.com> wrote:
>
> # first bad commit: [fb97d2eb542faf19a8725afbd75cbc2518903210]
> binfmt_elf, coredump: Log the reason of the failed core dumps
>
> I have to admit I don't immediately see what's wrong with the patch.
That commit looks entirely broken.
I *suspect* that the problem is the crazy "get_task_comm()" in that
takes the task lock inside coredump_report_failure().
But honestly, I'm not going to bother even trying to debug this. The
whole notion was broken. People who have problems with truncated
core-files should be looking at their debuggers, not asking the kernel
for help.
Linus
Powered by blists - more mailing lists