[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230629141719.4pwvpd4q5fow6zwu@moria.home.lan>
Date: Thu, 29 Jun 2023 10:17:19 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Christian Brauner <brauner@...nel.org>
Cc: Jens Axboe <axboe@...nel.dk>, Dave Chinner <david@...morbit.com>,
torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-bcachefs@...r.kernel.org,
Christoph Hellwig <hch@....de>,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [GIT PULL] bcachefs
On Thu, Jun 29, 2023 at 01:18:11PM +0200, Christian Brauner wrote:
> There seems to be a wild misconception here which frankly is very
> concering. Afaik, it is absolutely not the case that an fput() from an
> exiting task ends up in delayed_work(). But I'm happy to be convinced
> otherwise.
I already explained the real issue - it's fput() from an AIO completion,
because that has no association with task it was done on behalf of.
Powered by blists - more mailing lists