[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wj5_=m4DyZ=8==bfL2UCnWU=UDjQu-XCq_b92oDJh1i-Q@mail.gmail.com>
Date: Thu, 10 Jun 2021 14:04:04 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Olivier Langlois <olivier@...llion01.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
io-uring <io-uring@...r.kernel.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
Jens Axboe <axboe@...nel.dk>,
"Pavel Begunkov>" <asml.silence@...il.com>,
Oleg Nesterov <oleg@...hat.com>
Subject: Re: [PATCH] coredump: Limit what can interrupt coredumps
On Thu, Jun 10, 2021 at 1:11 PM Eric W. Biederman <ebiederm@...ssion.com> wrote:
>
> Make the coredump code more robust by explicitly testing for all of
> the wakeup conditions the coredump code supports. This prevents
> new wakeup conditions from breaking the coredump code, as well
> as fixing the current issue.
Thanks, applied.
And lots of thanks to Olivier who kept debugging the odd coredump
behavior he saw.
Linus
Powered by blists - more mailing lists