[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <170121485154.7109.13588704687316181624@noble.neil.brown.name>
Date: Wed, 29 Nov 2023 10:40:51 +1100
From: "NeilBrown" <neilb@...e.de>
To: "Oleg Nesterov" <oleg@...hat.com>
Cc: "Christian Brauner" <brauner@...nel.org>,
"Al Viro" <viro@...iv.linux.org.uk>,
"Jens Axboe" <axboe@...nel.dk>,
"Chuck Lever" <chuck.lever@...cle.com>,
"Jeff Layton" <jlayton@...nel.org>,
"Ingo Molnar" <mingo@...hat.com>,
"Peter Zijlstra" <peterz@...radead.org>,
"Juri Lelli" <juri.lelli@...hat.com>,
"Vincent Guittot" <vincent.guittot@...aro.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nfs@...r.kernel.org
Subject: Re: [PATCH/RFC] core/nfsd: allow kernel threads to use task_work.
On Wed, 29 Nov 2023, Oleg Nesterov wrote:
> Forgot to menstion,
>
> On 11/28, Oleg Nesterov wrote:
> >
> > but please
> > note irq_thread()->task_work_add(on_exit_work).
>
> and this means that Neil's and your more patch were wrong ;)
Yes it does - thanks for that!
I guess we need a setting that is focused particularly on fput().
Probably a PF flag is best for that.
Thanks,
NeilBrown
>
> Oleg.
>
>
Powered by blists - more mailing lists