From: Kay Sievers <kay.sievers@vrfy.org>
To: Matthew Wilcox <matthew@wil.cx>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
pjones@redhat.com
Subject: Re: [PATCH] Add a 'wait-scan' command to /proc/scsi/scsi.
Date: Thu, 26 Mar 2009 18:25:25 +0100 [thread overview]
Message-ID: <ac3eb2510903261025y5cacc8a3i32ba8ee8896c9db9@mail.gmail.com> (raw)
In-Reply-To: <20090326144716.GA5696@nostromo.devel.redhat.com>
On Thu, Mar 26, 2009 at 15:47, Bill Nottingham <notting@redhat.com> wrote:
> Matthew Wilcox (matthew@wil.cx) said:
>> > Well, in the case I'm looking at, udev is what's loading the host
>> > controllers, and there needs to be some sort of synchronization point
>> > between that and LVM invocations, fsck, mount, etc. Since scans
>> > aren't sent over as events for udev to catch, 'udevadm settle'
>> > isn't enough.
>>
>> So ... if we sent a udev event when the scan list was empty, you'd be OK?
>
> I'm CC'ing Peter, who has some more ideas - it would definitely be a good
> start, but we'd probably at least need to know when the scan list started
> being filled as well.
I don't like to see any uevent send for issues like this. This would
just be a hack around badly designed system services, which should be
fixed themselves and not worked around in the kernel. This hack will
run useless events for system who don't need them.
Something like a poll()'able sysfs file, which other subsytems already
use, and which can be used to wake up a process that can blocks, might
work fine here.
Thanks,
Kay
prev parent reply other threads:[~2009-03-26 17:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 19:00 Bill Nottingham
2009-03-25 19:00 ` [PATCH] Declare PIO_CMAP/GIO_CMAP as compatbile ioctls Bill Nottingham
2009-03-25 19:02 ` Bill Nottingham
2009-03-25 19:01 ` [PATCH] Add a 'wait-scan' command to /proc/scsi/scsi Christoph Hellwig
2009-03-25 19:03 ` Bill Nottingham
2009-03-25 19:26 ` Matthew Wilcox
2009-03-25 19:47 ` Bill Nottingham
2009-03-25 20:36 ` Matthew Wilcox
2009-03-26 14:47 ` Bill Nottingham
2009-03-26 17:25 ` Kay Sievers [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=ac3eb2510903261025y5cacc8a3i32ba8ee8896c9db9@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=pjones@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®