[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgdBfqyNHk0iNyYpEuBUdVgq1KMzHMuEqn=ADtfyK_pkQ@mail.gmail.com>
Date: Mon, 12 Jun 2023 09:42:15 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jens Axboe <axboe@...nel.dk>
Cc: "Darrick J. Wong" <djwong@...nel.org>,
Dave Chinner <david@...morbit.com>,
Zorro Lang <zlang@...hat.com>, linux-xfs@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Mike Christie <michael.christie@...cle.com>,
"Michael S. Tsirkin" <mst@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [6.5-rc5 regression] core dump hangs (was Re: [Bug report]
fstests generic/051 (on xfs) hang on latest linux v6.5-rc5+)
On Mon, Jun 12, 2023 at 9:38 AM Jens Axboe <axboe@...nel.dk> wrote:
>
> Quick peek would suggest that it's because io-wq clears PF_IO_WORKER on
> exit, and now we fail the check in coredump_task_exit() that was added.
Oh, that makes sense.
Well, it makes sense for the bug, but that whole
preempt_disable();
current->flags &= ~PF_IO_WORKER;
preempt_enable();
thin in io_worker_exit() does *not* make sense to me.
Does removing those three lines make things "JustWork(tm)"?
Linus
Powered by blists - more mailing lists