[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025042305-timid-unusable-0501@gregkh>
Date: Wed, 23 Apr 2025 08:42:34 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Christian Brauner <brauner@...nel.org>
Cc: Christoph Hellwig <hch@....de>, rafael@...nel.org, dakr@...nel.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
hca@...ux.ibm.com,
Shin'ichiro Kawasaki <shinichiro.kawasaki@....com>,
Xiao Ni <xni@...hat.com>
Subject: Re: [PATCH] devtmpfs: don't use vfs_getattr_nosec to query i_mode
On Wed, Apr 23, 2025 at 07:54:51AM +0200, Christian Brauner wrote:
> On Wed, Apr 23, 2025 at 06:59:41AM +0200, Christoph Hellwig wrote:
> > The recent move of the bdev_statx call to the low-level vfs_getattr_nosec
> > helper caused it being used by devtmpfs, which leads to deadlocks in
> > md teardown due to the block device lookup and put interfering with the
> > unusual lifetime rules in md.
> >
> > But as handle_remove only works on inodes created and owned by devtmpfs
> > itself there is no need to use vfs_getattr_nosec vs simply reading the
> > mode from the inode directly. Switch to that to avoid the bdev lookup
> > or any other unintentional side effect.
> >
> > Reported-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@....com>
> > Reported-by: Xiao Ni <xni@...hat.com>
> > Fixes: 777d0961ff95 ("fs: move the bdex_statx call to vfs_getattr_nosec")
> > Signed-off-by: Christoph Hellwig <hch@....de>
> > Tested-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@....com>
> > Tested-by: Xiao Ni <xni@...hat.com>
> > ---
>
> Reviewed-by: Christian Brauner <brauner@...nel.org>
Do you want me to take this through the driver-core tree, or is this a
fs-specific thing as that's where the regression showed up from? Either
is fine with me.
thanks,
greg k-h
Powered by blists - more mailing lists