From: Harald Hoyer <harald@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: Jes.Sorensen@redhat.com, linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/1] prevent double open(O_RDWR) on raid creation
Date: Mon, 29 Apr 2013 07:33:21 +0200 [thread overview]
Message-ID: <517E0621.5030700@redhat.com> (raw)
In-Reply-To: <20130429105720.593fe99b@notabene.brown>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/29/2013 02:57 AM, NeilBrown wrote:
> On Thu, 11 Apr 2013 15:18:33 +0200 Jes.Sorensen@redhat.com wrote:
>
>> From: Harald Hoyer <harald@redhat.com>
>>
>> This does not trigger the udev inotify twice and saves a lot of blk I/O
>> for the raid members.
>>
>> Also fixes: https://bugzilla.redhat.com/show_bug.cgi?id=947815
>>
>> Signed-off-by: Harald Hoyer <harald@redhat.com> Signed-off-by: Jes
>> Sorensen <Jes.Sorensen@redhat.com>
>
> (Sorry for delays. Thanks for reminders).
>
> That patch seems to make sense, but the description above is awfully thin.
>
> Why is double-open a problem exactly? What does it make udev do? And how
> does that related to ID_FS_TYPE being wrong as mentioned in the bugzilla
> entry.
>
> NeilBrown
>
udevd with watch enabled (inotify on /dev/sd*) gets triggered on close(), when
you opened it writeable. So, if you double open() and udev wakes up from the
first close(), not all information are written to disk yet, it will not get
the ID_FS_TYPE.
Seems like the second close() does not trigger an inotify sometimes, so it is
missing afterwards all the time.
Watch via inotify is just a lazy workaround, so we don't have to modify every
tool to emit a "change" uevent, after they changed the disk.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRfgYhAAoJEANOs3ABTfJw0uUQALrm0pEjlLd6XgojMTQ6xJGy
y98MVcobi10O/WJyg3HV1RqjnYNu7wfpp+lFIzKRmE/sxIBj8X9ATFfjaopCGWYC
/MPGsdehrCpGPPOZBlt47vTdoaKWB5meKsBm3X1I0AhA+uOxgeV2qfaijoOkHeim
a4RbIUoOJIjIyvbdKCuVbs8mqcr62eMUiZBDPv/b3FcBtOOjYkWVZU14ylqujNtM
WzE+soKyd6L70DvPWVY2KzJ4/5bg/fRuvFcc464k88hAqa8U36FU6MzfTuT4K+ZH
a4FYJtpdrggL+IZuG5XToNR5lpR/YW/B1UBhfCjItXbr1dhX3alk+Y3xZCWvpbRF
FFwAA1GJfcB8UmKp3loBX0YH4gJ8h8d6EITE0Quj38VqG4MlCl89J6ClQZYgXsf8
ZCVDX+lomiQkEp5xYyC85hmwfwepibncqfqKef8+4ABc5xWswQr89gDFPVsFZUE/
PbHzCUlAkz8lvuRSNH6k54b7nFeGn116eJgO7sKESt4uygP0o1A6WpWZI+YAMMg5
CBkxrLYM/iERP7sf8kHr3Wd5EWJNTYm6UsJjVtWStGHuB7LNDo6qPBXxzf84Mkek
1fnIqBfl6QDQBcYb+02p2vGhcTA+P/byi+j+eFQmwV8g2gbkwxhV6/t0Sizj57tC
SlUZAaWHeeNK9HDgoNJ0
=zkJO
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-04-29 5:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 13:18 [PATCH 0/1] Reduce unnecessary opens of raid members Jes.Sorensen
2013-04-11 13:18 ` [PATCH 1/1] prevent double open(O_RDWR) on raid creation Jes.Sorensen
2013-04-29 0:57 ` NeilBrown
2013-04-29 5:33 ` Harald Hoyer [this message]
2013-04-29 6:11 ` NeilBrown
2013-04-29 6:32 ` Harald Hoyer
2013-04-29 6:53 ` NeilBrown
2013-04-29 8:34 ` Harald Hoyer
2013-04-29 8:40 ` Harald Hoyer
2013-04-29 8:45 ` Harald Hoyer
2013-04-29 8:54 ` Harald Hoyer
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=517E0621.5030700@redhat.com \
--to=harald@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).