From: Rusty Russell <rusty@rustcorp.com.au>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>,
mst@redhat.com, Milos Vyletel <milos.vyletel@sde.cz>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio-blk: emit udev event when device is resized
Date: Fri, 22 Feb 2013 10:14:49 +1030 [thread overview]
Message-ID: <87y5ehfczy.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1361473348-7660-1-git-send-email-milos.vyletel@sde.cz>
Milos Vyletel <milos.vyletel@sde.cz> writes:
> When virtio-blk device is resized from host (using block_resize from QEMU) emit
> KOBJ_CHANGE uevent to notify guest about such change. This allows user to have
> custom udev rules which would take whatever action if such event occurs. As a
> proof of concept I've created simple udev rule that automatically resize
> filesystem on virtio-blk device.
>
> ACTION=="change", KERNEL=="vd*", \
> ENV{RESIZE}=="1", \
> ENV{ID_FS_TYPE}=="ext[3-4]", \
> RUN+="/sbin/resize2fs /dev/%k"
> ACTION=="change", KERNEL=="vd*", \
> ENV{RESIZE}=="1", \
> ENV{ID_FS_TYPE}=="LVM2_member", \
> RUN+="/sbin/pvresize /dev/%k"
This looks fine to me, but I like to check with Greg before adding udev
callouts.... Greg?
BTW, if this is good, it's good for stable IMHO.
Cheers,
Rusty.
> Signed-off-by: Milos Vyletel <milos.vyletel@sde.cz>
> ---
> drivers/block/virtio_blk.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
> index 8ad21a2..5990382 100644
> --- a/drivers/block/virtio_blk.c
> +++ b/drivers/block/virtio_blk.c
> @@ -539,6 +539,8 @@ static void virtblk_config_changed_work(struct work_struct *work)
> struct virtio_device *vdev = vblk->vdev;
> struct request_queue *q = vblk->disk->queue;
> char cap_str_2[10], cap_str_10[10];
> + char event[] = "RESIZE=1";
> + char *envp[] = { event, NULL };
> u64 capacity, size;
>
> mutex_lock(&vblk->config_lock);
> @@ -568,6 +570,7 @@ static void virtblk_config_changed_work(struct work_struct *work)
>
> set_capacity(vblk->disk, capacity);
> revalidate_disk(vblk->disk);
> + kobject_uevent_env(&disk_to_dev(vblk->disk)->kobj, KOBJ_CHANGE, envp);
> done:
> mutex_unlock(&vblk->config_lock);
> }
> --
> 1.7.1
WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Milos Vyletel <milos.vyletel@sde.cz>, linux-kernel@vger.kernel.org
Cc: virtualization@lists.linux-foundation.org, mst@redhat.com,
Milos Vyletel <milos.vyletel@sde.cz>, "Greg KH" <greg@kroah.com>
Subject: Re: [PATCH] virtio-blk: emit udev event when device is resized
Date: Fri, 22 Feb 2013 10:14:49 +1030 [thread overview]
Message-ID: <87y5ehfczy.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1361473348-7660-1-git-send-email-milos.vyletel@sde.cz>
Milos Vyletel <milos.vyletel@sde.cz> writes:
> When virtio-blk device is resized from host (using block_resize from QEMU) emit
> KOBJ_CHANGE uevent to notify guest about such change. This allows user to have
> custom udev rules which would take whatever action if such event occurs. As a
> proof of concept I've created simple udev rule that automatically resize
> filesystem on virtio-blk device.
>
> ACTION=="change", KERNEL=="vd*", \
> ENV{RESIZE}=="1", \
> ENV{ID_FS_TYPE}=="ext[3-4]", \
> RUN+="/sbin/resize2fs /dev/%k"
> ACTION=="change", KERNEL=="vd*", \
> ENV{RESIZE}=="1", \
> ENV{ID_FS_TYPE}=="LVM2_member", \
> RUN+="/sbin/pvresize /dev/%k"
This looks fine to me, but I like to check with Greg before adding udev
callouts.... Greg?
BTW, if this is good, it's good for stable IMHO.
Cheers,
Rusty.
> Signed-off-by: Milos Vyletel <milos.vyletel@sde.cz>
> ---
> drivers/block/virtio_blk.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
> index 8ad21a2..5990382 100644
> --- a/drivers/block/virtio_blk.c
> +++ b/drivers/block/virtio_blk.c
> @@ -539,6 +539,8 @@ static void virtblk_config_changed_work(struct work_struct *work)
> struct virtio_device *vdev = vblk->vdev;
> struct request_queue *q = vblk->disk->queue;
> char cap_str_2[10], cap_str_10[10];
> + char event[] = "RESIZE=1";
> + char *envp[] = { event, NULL };
> u64 capacity, size;
>
> mutex_lock(&vblk->config_lock);
> @@ -568,6 +570,7 @@ static void virtblk_config_changed_work(struct work_struct *work)
>
> set_capacity(vblk->disk, capacity);
> revalidate_disk(vblk->disk);
> + kobject_uevent_env(&disk_to_dev(vblk->disk)->kobj, KOBJ_CHANGE, envp);
> done:
> mutex_unlock(&vblk->config_lock);
> }
> --
> 1.7.1
next prev parent reply other threads:[~2013-02-21 23:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 19:02 [PATCH] virtio-blk: emit udev event when device is resized Milos Vyletel
2013-02-21 23:44 ` Rusty Russell [this message]
2013-02-21 23:44 ` Rusty Russell
2013-02-25 22:12 ` Greg KH
2013-02-25 22:12 ` Greg KH
2013-02-25 22:12 ` Greg KH
2013-02-25 22:39 ` Kay Sievers
2013-02-25 22:39 ` Kay Sievers
2013-02-25 22:43 ` Greg KH
2013-02-25 22:43 ` Greg KH
2013-02-25 22:43 ` Greg KH
2013-02-25 23:04 ` Kay Sievers
2013-02-25 23:04 ` Kay Sievers
2013-02-25 23:04 ` Kay Sievers
2013-02-25 23:38 ` Milos Vyletel
2013-02-25 23:38 ` Milos Vyletel
2013-02-25 23:38 ` Milos Vyletel
2013-02-25 22:39 ` Kay Sievers
2013-02-25 23:41 ` Milos Vyletel
2013-02-25 23:41 ` Milos Vyletel
2013-02-25 23:41 ` Milos Vyletel
2013-02-27 0:34 ` Rusty Russell
2013-02-27 0:46 ` Rusty Russell
2013-02-27 0:34 ` Rusty Russell
2013-02-27 13:09 ` Milos Vyletel
2013-02-27 13:09 ` Milos Vyletel
2013-02-27 13:09 ` Milos Vyletel
2013-02-25 7:43 ` Asias He
2013-02-25 7:43 ` Asias He
2013-02-25 14:54 ` Milos Vyletel
2013-02-25 14:54 ` Milos Vyletel
2013-02-26 3:09 ` Asias He
2013-02-26 3:09 ` Asias He
2013-02-26 13:05 ` Milos Vyletel
2013-02-26 13:05 ` Milos Vyletel
2013-02-27 0:37 ` Rusty Russell
2013-02-27 0:37 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2013-02-21 19:02 Milos Vyletel
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=87y5ehfczy.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=milos.vyletel@sde.cz \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.