From: Hannes Reinecke <hare@suse.de>
To: Milan Broz <mbroz@redhat.com>
Cc: Nikanth Karthikesan <knikanth@suse.de>,
device-mapper development <dm-devel@redhat.com>,
Alasdair G Kergon <agk@redhat.com>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [PATCH][RFC] Emulate BLKRRPART on device-mapper
Date: Wed, 22 Jul 2009 10:19:33 +0200 [thread overview]
Message-ID: <4A66CB95.7060806@suse.de> (raw)
In-Reply-To: <4A66CA08.9080509@redhat.com>
Milan Broz wrote:
> Hannes Reinecke wrote:
>>> + /* partitions handled in userspace, just send change event */
>>> + if (disk_userspace_partitions(disk)) {
>>> + kobject_uevent(&disk_to_dev(disk)->kobj, KOBJ_CHANGE);
>>> + return 0;
>>> + }
>>> +
>> Wrong. If you do it here, you'll never be able to catch any size changes
>> of the disk. You'll have to move it to after the 'bdev->bd_invalidated = 0'
>> line.
>
> Yes, for non-DM devices which want to use that flag.
>
> For device-mapper device, size can change only by mapping table change
> which always generate change uevent.
>
Okay. But the whole point of my objections is to make the flag useable
for the general populace, so that my second patch can take advantage
of it.
>> I would suggest renaming it to GENHD_FL_USERSPACE_PARTITIONS, as this is
>> more in line with the function of the flag.
>
> no problem here:-)
Hmm. I've send an updated patch, but it seems to be stuck in the mailqueue
somewhere.
The second patch went through, though ... curious.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
prev parent reply other threads:[~2009-07-22 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 8:44 [PATCH] Emulate BLKRRPART on device-mapper Nikanth Karthikesan
2009-07-20 18:23 ` Alasdair G Kergon
2009-07-21 16:13 ` [PATCH][RFC] " Milan Broz
2009-07-22 7:06 ` Hannes Reinecke
2009-07-22 8:12 ` Milan Broz
2009-07-22 8:19 ` Hannes Reinecke [this message]
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=4A66CB95.7060806@suse.de \
--to=hare@suse.de \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=knikanth@suse.de \
--cc=mbroz@redhat.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 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.