From: Christoph Hellwig <hch@lst.de>
To: Balbir Singh <sblbir@amazon.com>
Cc: axboe@kernel.dk, mst@redhat.com, jejb@linux.ibm.com,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org,
Someswarudu Sangaraju <ssomesh@amazon.com>,
hch@lst.de
Subject: Re: [RFC PATCH] block/genhd: Notify udev about capacity change
Date: Thu, 12 Dec 2019 10:54:31 +0100 [thread overview]
Message-ID: <20191212095431.GA3720@lst.de> (raw)
In-Reply-To: <20191210030131.4198-1-sblbir@amazon.com>
On Tue, Dec 10, 2019 at 03:01:31AM +0000, Balbir Singh wrote:
> Allow block/genhd to notify user space (via udev) about disk size changes
> using a new helper disk_set_capacity(), which is a wrapper on top
> of set_capacity(). disk_set_capacity() will only notify via udev if
> the current capacity or the target capacity is not zero.
>
> disk_set_capacity() is not enabled for all devices, just virtio block,
> xen-blockfront, nvme and sd. Owners of other block disk devices can
> easily move over by changing set_capacity() to disk_set_capacity()
>
> Background:
>
> As a part of a patch to allow sending the RESIZE event on disk capacity
> change, Christoph (hch@lst.de) requested that the patch be made generic
> and the hacks for virtio block and xen block devices be removed and
> merged via a generic helper.
>
> Testing:
> 1. I did some basic testing with an NVME device, by resizing it in
> the backend and ensured that udevd received the event.
>
> Suggested-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Balbir Singh <sblbir@amazon.com>
> Signed-off-by: Someswarudu Sangaraju <ssomesh@amazon.com>
> ---
> block/genhd.c | 19 +++++++++++++++++++
> drivers/block/virtio_blk.c | 4 +---
> drivers/block/xen-blkfront.c | 5 +----
> drivers/nvme/host/core.c | 2 +-
> drivers/scsi/sd.c | 2 +-
> include/linux/genhd.h | 1 +
> 6 files changed, 24 insertions(+), 9 deletions(-)
>
> diff --git a/block/genhd.c b/block/genhd.c
> index ff6268970ddc..94faec98607b 100644
> --- a/block/genhd.c
> +++ b/block/genhd.c
> @@ -46,6 +46,25 @@ static void disk_add_events(struct gendisk *disk);
> static void disk_del_events(struct gendisk *disk);
> static void disk_release_events(struct gendisk *disk);
>
> +/*
> + * Set disk capacity and notify if the size is not currently
> + * zero and will not be set to zero
Nit: Use up all the 80 chars per line. Also maybe turn this into a
kerneldoc comment. I think you also want to mention the notification
as well.
> +EXPORT_SYMBOL_GPL(disk_set_capacity);
> +
> +
> void part_inc_in_flight(struct request_queue *q, struct hd_struct *part, int rw)
No need for the double empty line.
> {
> if (queue_is_mq(q))
> diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
> index 7ffd719d89de..869cd3c31529 100644
> --- a/drivers/block/virtio_blk.c
> +++ b/drivers/block/virtio_blk.c
And you probably want to turn this into a series with patch 1 adding
the infrastructure, and then one patch per driver switched over.
_______________________________________________
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-12 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 3:01 [RFC PATCH] block/genhd: Notify udev about capacity change Balbir Singh
2019-12-11 19:36 ` Singh, Balbir
2019-12-12 9:54 ` Christoph Hellwig [this message]
2019-12-13 9:13 ` 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=20191212095431.GA3720@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=jejb@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mst@redhat.com \
--cc=sblbir@amazon.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).