From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Naohiro Aota <naohiro.aota@wdc.com>,
linux-block@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: [PATCH 7/9] loop: don't grab a reference to the block device
Date: Thu, 22 Jul 2021 09:54:00 +0200 [thread overview]
Message-ID: <20210722075402.983367-8-hch@lst.de> (raw)
In-Reply-To: <20210722075402.983367-1-hch@lst.de>
The whole device block device won't be removed while the disk is still
alive, so don't bother to grab a reference to it.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
---
drivers/block/loop.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index f37b9e3d833c..62c5120cf744 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -1249,10 +1249,6 @@ static int loop_configure(struct loop_device *lo, fmode_t mode,
if (partscan)
lo->lo_disk->flags &= ~GENHD_FL_NO_PART_SCAN;
- /* Grab the block_device to prevent its destruction after we
- * put /dev/loopXX inode. Later in __loop_clr_fd() we bdput(bdev).
- */
- bdgrab(bdev);
mutex_unlock(&lo->lo_mutex);
if (partscan)
loop_reread_partitions(lo);
@@ -1332,7 +1328,6 @@ static int __loop_clr_fd(struct loop_device *lo, bool release)
blk_queue_physical_block_size(lo->lo_queue, 512);
blk_queue_io_min(lo->lo_queue, 512);
if (bdev) {
- bdput(bdev);
invalidate_bdev(bdev);
bdev->bd_inode->i_mapping->wb_err = 0;
}
--
2.30.2
next prev parent reply other threads:[~2021-07-22 7:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 7:53 fixes and cleanups for block_device refcounting v2 Christoph Hellwig
2021-07-22 7:53 ` [PATCH 1/9] block: delay freeing the gendisk Christoph Hellwig
2021-07-22 7:53 ` [PATCH 2/9] block: assert the locking state in delete_partition Christoph Hellwig
2021-07-22 18:38 ` Chaitanya Kulkarni
2021-07-22 7:53 ` [PATCH 3/9] block: unhash the whole device inode earlier Christoph Hellwig
2021-07-22 8:19 ` Ming Lei
2021-07-22 13:12 ` Christoph Hellwig
2021-07-22 7:53 ` [PATCH 4/9] block: allocate bd_meta_info later in add_partitions Christoph Hellwig
2021-07-22 8:32 ` Ming Lei
2021-07-22 7:53 ` [PATCH 5/9] block: change the refcounting for partitions Christoph Hellwig
2021-07-22 8:41 ` Ming Lei
2021-07-22 13:12 ` Christoph Hellwig
2021-07-22 7:53 ` [PATCH 6/9] btrfs: store a block_device in struct btrfs_ordered_extent Christoph Hellwig
2021-07-22 12:58 ` David Sterba
2021-07-22 13:04 ` Christoph Hellwig
2021-07-22 7:54 ` Christoph Hellwig [this message]
2021-07-22 8:57 ` [PATCH 7/9] loop: don't grab a reference to the block device Ming Lei
2021-07-22 18:40 ` Chaitanya Kulkarni
2021-07-22 7:54 ` [PATCH 8/9] block: remove bdgrab Christoph Hellwig
2021-07-22 7:54 ` [PATCH 9/9] block: remove bdput Christoph Hellwig
2021-07-22 18:40 ` Chaitanya Kulkarni
2021-07-28 1:39 ` fixes and cleanups for block_device refcounting v2 Jens Axboe
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=20210722075402.983367-8-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.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;
as well as URLs for NNTP newsgroup(s).