[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wi3ucaR0GXt6iaAX6tKO=iHcbe6jDzf2Mgz1petZMc=rw@mail.gmail.com>
Date: Mon, 12 Jun 2023 09:45:22 -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:42 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> 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.
Oh, it looks like that goes back to the original io_worker
implementation, when io_worker_start() would set the PF_IO_WORKER bit,
and io_worker_exit() would clear it, and they were otherwise created
like normal kthreads.
It *looks* all entirely historical to me, and removing those three
lines as left-over baggage smells like the right thing.
Linus
Powered by blists - more mailing lists