From: Balbir Singh <sblbir@amazon.com>
To: <=linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-nvme@lists.infradead.org>
Cc: axboe@kernel.dk, mst@redhat.com, jejb@linux.ibm.com,
ssomesh@amazon.com, Balbir Singh <sblbir@amazon.com>,
hch@lst.de
Subject: [RFC PATCH 2/5] drivers/block/virtio_blk.c: Convert to use disk_set_capacity
Date: Mon, 23 Dec 2019 01:40:53 +0000 [thread overview]
Message-ID: <20191223014056.17318-2-sblbir@amazon.com> (raw)
In-Reply-To: <20191223014056.17318-1-sblbir@amazon.com>
block/genhd provides disk_set_capacity() for sending
RESIZE notifications via uevents.
Signed-off-by: Balbir Singh <sblbir@amazon.com>
---
drivers/block/virtio_blk.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
index fbbf18ac1d5d..9848c94a7eb4 100644
--- a/drivers/block/virtio_blk.c
+++ b/drivers/block/virtio_blk.c
@@ -479,18 +479,16 @@ static void virtblk_update_capacity(struct virtio_blk *vblk, bool resize)
cap_str_10,
cap_str_2);
- set_capacity(vblk->disk, capacity);
+ disk_set_capacity(vblk->disk, capacity);
}
static void virtblk_config_changed_work(struct work_struct *work)
{
struct virtio_blk *vblk =
container_of(work, struct virtio_blk, config_work);
- char *envp[] = { "RESIZE=1", NULL };
virtblk_update_capacity(vblk, true);
revalidate_disk(vblk->disk);
- kobject_uevent_env(&disk_to_dev(vblk->disk)->kobj, KOBJ_CHANGE, envp);
}
static void virtblk_config_changed(struct virtio_device *vdev)
--
2.16.5
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-12-23 1:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 1:40 [RFC PATCH 1/5] block/genhd: Notify udev about capacity change Balbir Singh
2019-12-23 1:40 ` Balbir Singh [this message]
2019-12-23 1:40 ` [RFC PATCH 3/5] drivers/block/xen-blkfront.c: Convert to use disk_set_capacity Balbir Singh
2019-12-23 1:40 ` [RFC PATCH 4/5] drivers/nvme/host/core.c: " Balbir Singh
2019-12-23 1:40 ` [RFC PATCH 5/5] drivers/scsi/sd.c: " Balbir Singh
2019-12-23 1:53 ` [RFC PATCH 1/5] block/genhd: Notify udev about capacity change Singh, Balbir
2020-01-01 3:26 ` Chaitanya Kulkarni
2020-01-02 7:36 ` Singh, Balbir
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=20191223014056.17318-2-sblbir@amazon.com \
--to=sblbir@amazon.com \
--cc==linux-block@vger.kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mst@redhat.com \
--cc=ssomesh@amazon.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).