From: Christoph Hellwig <hch@infradead.org>
To: Anand Jain <anand.jain@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
boris@bur.io, dsterba@suse.com, linux-btrfs@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: validate device maj:min during open
Date: Fri, 8 Mar 2024 08:10:51 -0800 [thread overview]
Message-ID: <Zes4i3qvFk2nWjyY@infradead.org> (raw)
In-Reply-To: <be3571d7-2bfe-4bad-b2c6-84a0bf121140@oracle.com>
On Fri, Mar 08, 2024 at 09:34:03PM +0530, Anand Jain wrote:
> > bdev_open_by_path. bdev_open_by_path bdev_open_by_path calls
> > lookup_bdev to translate the path to a dev_t and then calls
> > bdev_open_by_dev on the dev_t, which stored the passes in dev_t in
> > bdev->bd_dev. I see absolutely no way how this check could ever
> > trigger.
> >
>
> Prior to this patch, the device->devt value of the device could become
> stale, as it might not have been updated since the last scan of the
> device. During this interval, the device could have undergone changes
> to its devt.
How can it become stale here? btrfs_open_one_device exits early
if device->bdev is set, so you set up a new device->bdev and
stash the just opened bdev there. The dev_t of an existing
struct block_device never changes, so it must match the one
in the btrfs_device that was just initialized from it.
next prev parent reply other threads:[~2024-03-08 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 2:45 [PATCH v2] btrfs: validate device maj:min during open Anand Jain
2024-03-08 15:48 ` Christoph Hellwig
2024-03-08 16:04 ` Anand Jain
2024-03-08 16:10 ` Christoph Hellwig [this message]
2024-03-08 16:23 ` Anand Jain
2024-03-08 17:23 ` Christoph Hellwig
2024-03-08 17:32 ` Boris Burkov
2024-03-08 17:42 ` Christoph Hellwig
2024-03-08 17:51 ` Boris Burkov
2024-03-13 16:24 ` Anand Jain
2024-03-08 17:41 ` Boris Burkov
2024-03-12 19:17 ` Boris Burkov
2024-03-13 10:25 ` Anand Jain
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=Zes4i3qvFk2nWjyY@infradead.org \
--to=hch@infradead.org \
--cc=anand.jain@oracle.com \
--cc=boris@bur.io \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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