From: Jan Kara <jack@suse.cz>
To: Christian Brauner <brauner@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Jan Kara <jack@suse.cz>,
Jens Axboe <axboe@kernel.dk>,
Matthew Wilcox <willy@infradead.org>,
linux-block@vger.kernel.org
Subject: Re: [PATCH 2/2] [RFC]: block: count BLK_OPEN_RESTRICT_WRITES openers
Date: Tue, 26 Mar 2024 14:24:35 +0100 [thread overview]
Message-ID: <20240326132435.fy7dh5p6mhagohtw@quack3> (raw)
In-Reply-To: <20240323-abtauchen-klauen-c2953810082d@brauner>
On Sat 23-03-24 17:11:20, Christian Brauner wrote:
> The original changes in v6.8 do allow for a block device to be reopened
> with BLK_OPEN_RESTRICT_WRITES provided the same holder is used as per
> bdev_may_open(). I think that may have a bug.
^^^^^^^^ is :)
Also AFAICT this can happen only the the reopen is O_RDONLY which would be
probably good to mention here.
> The first opener @f1 of that block device will set bdev->bd_writers to
> -1. The second opener @f2 using the same holder will pass the check in
> bdev_may_open() that bdev->bd_writers must not be greater than zero.
>
> The first opener @f1 now closes the block device and in bdev_release()
> will end up calling bdev_yield_write_access() which calls
> bdev_writes_blocked() and sets bdev->bd_writers to 0 again.
>
> Now @f2 holds a file to that block device which was opened with
> exclusive write access but bdev->bd_writers has been reset to 0.
>
> So now @f3 comes along and succeeds in opening the block device with
> BLK_OPEN_WRITE betraying @f2's request to have exclusive write access.
>
> This isn't a practical issue yet because afaict there's no codepath
> inside the kernel that reopenes the same block device with
> BLK_OPEN_RESTRICT_WRITES but it will be if there is.
>
> If that's right then fix this by counting the number of
> BLK_OPEN_RESTRICT_WRITES openers. So we only allow writes again once all
> BLK_OPEN_RESTRICT_WRITES openers are done.
>
> Fixes: ed5cc702d311 ("block: Add config option to not allow writing to mounted devices")
> Signed-off-by: Christian Brauner <brauner@kernel.org>
Otherwise looks good so feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> block/bdev.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/block/bdev.c b/block/bdev.c
> index f819f3086905..42f84692404c 100644
> --- a/block/bdev.c
> +++ b/block/bdev.c
> @@ -776,17 +776,17 @@ void blkdev_put_no_open(struct block_device *bdev)
>
> static bool bdev_writes_blocked(struct block_device *bdev)
> {
> - return bdev->bd_writers == -1;
> + return bdev->bd_writers < 0;
> }
>
> static void bdev_block_writes(struct block_device *bdev)
> {
> - bdev->bd_writers = -1;
> + bdev->bd_writers--;
> }
>
> static void bdev_unblock_writes(struct block_device *bdev)
> {
> - bdev->bd_writers = 0;
> + bdev->bd_writers++;
> }
>
> static bool bdev_may_open(struct block_device *bdev, blk_mode_t mode)
> --
> 2.43.0
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-03-26 13:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 14:54 [PATCH] block: handle BLK_OPEN_RESTRICT_WRITES correctly Christian Brauner
2024-03-23 15:59 ` Christian Brauner
2024-03-23 16:11 ` [PATCH 1/2] " Christian Brauner
2024-03-23 16:11 ` [PATCH 2/2] [RFC]: block: count BLK_OPEN_RESTRICT_WRITES openers Christian Brauner
2024-03-26 13:24 ` Jan Kara [this message]
2024-03-25 11:51 ` [PATCH 1/2] block: handle BLK_OPEN_RESTRICT_WRITES correctly Yu Kuai
2024-03-25 12:04 ` Christian Brauner
2024-03-25 13:52 ` Yu Kuai
2024-03-25 13:54 ` Christian Brauner
2024-03-26 1:32 ` Yu Kuai
2024-03-26 12:57 ` Jan Kara
2024-03-26 13:17 ` Christian Brauner
2024-03-26 13:31 ` Jan Kara
2024-03-26 15:46 ` [PATCH v2] " Christian Brauner
2024-03-26 17:25 ` Christoph Hellwig
2024-03-26 22:42 ` Jan Kara
2024-03-26 15:47 ` [PATCH 1/2] " Christian Brauner
2024-03-27 12:01 ` Christian Brauner
2024-03-29 4:56 ` Matthew Wilcox
2024-03-29 12:10 ` Christian Brauner
2024-03-29 15:11 ` Christian Brauner
2024-03-29 15:24 ` Christian Brauner
2024-04-03 6:04 ` Christian Brauner
2024-04-03 19:22 ` Matthew Wilcox
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=20240326132435.fy7dh5p6mhagohtw@quack3 \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=willy@infradead.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