From: Christian Brauner <brauner@kernel.org>
To: Heiko Carstens <hca@linux.ibm.com>, Christoph Hellwig <hch@lst.de>
Cc: gregkh@linuxfoundation.org, rafael@kernel.org, dakr@kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Xiao Ni <xni@redhat.com>
Subject: Re: [PATCH] devtmpfs: don't use vfs_getattr_nosec to query i_mode
Date: Fri, 25 Apr 2025 12:12:36 +0200 [thread overview]
Message-ID: <20250425-stehlen-koexistieren-c0f650dcccec@brauner> (raw)
In-Reply-To: <20250425100304.7180Ea5-hca@linux.ibm.com>
On Fri, Apr 25, 2025 at 12:03:04PM +0200, Heiko Carstens 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@wdc.com>
> > Reported-by: Xiao Ni <xni@redhat.com>
> > Fixes: 777d0961ff95 ("fs: move the bdex_statx call to vfs_getattr_nosec")
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > Tested-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> > Tested-by: Xiao Ni <xni@redhat.com>
> > ---
> > drivers/base/devtmpfs.c | 20 ++++++++------------
> > 1 file changed, 8 insertions(+), 12 deletions(-)
>
> ...
>
> > @@ -330,11 +329,8 @@ static int handle_remove(const char *nodename, struct device *dev)
> > if (IS_ERR(dentry))
> > return PTR_ERR(dentry);
> >
> > - p.mnt = parent.mnt;
> > - p.dentry = dentry;
> > - err = vfs_getattr(&p, &stat, STATX_TYPE | STATX_MODE,
> > - AT_STATX_SYNC_AS_STAT);
> > - if (!err && dev_mynode(dev, d_inode(dentry), &stat)) {
> > + inode = d_inode(dentry);
> > + if (dev_mynode(dev, inode)) {
>
> clang rightfully complains:
>
> CC drivers/base/devtmpfs.o
> drivers/base/devtmpfs.c:333:6: warning: variable 'err' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
> 333 | if (dev_mynode(dev, inode)) {
> | ^~~~~~~~~~~~~~~~~~~~~~
> drivers/base/devtmpfs.c:358:9: note: uninitialized use occurs here
> 358 | return err;
> | ^~~
> drivers/base/devtmpfs.c:333:2: note: remove the 'if' if its condition is always true
> 333 | if (dev_mynode(dev, inode)) {
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> drivers/base/devtmpfs.c:326:9: note: initialize the variable 'err' to silence this warning
> 326 | int err;
> | ^
> | = 0
>
> That is: if dev_mynode(dev, inode) is not true some random value will be returned.
Don't bother resending, Christoph.
I've already fixed this with int err = 0 in the tree.
next prev parent reply other threads:[~2025-04-25 10:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 4:59 Christoph Hellwig
2025-04-23 5:54 ` Christian Brauner
2025-04-23 6:42 ` Greg KH
2025-04-24 8:40 ` Christian Brauner
2025-04-23 6:45 ` Heiko Carstens
2025-04-24 5:07 ` Jain, Ayush
2025-04-24 8:41 ` Christian Brauner
2025-04-25 10:03 ` Heiko Carstens
2025-04-25 10:12 ` Christian Brauner [this message]
2025-04-25 13:32 ` Christoph Hellwig
2025-04-25 15:40 ` Kees Cook
2025-04-25 17:17 ` Nathan Chancellor
2025-04-28 13:15 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250425-stehlen-koexistieren-c0f650dcccec@brauner \
--to=brauner@kernel.org \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=xni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®