From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev - Shouldn't we blacklist some devices?
Date: Sun, 04 Jan 2004 00:07:49 +0000 [thread overview]
Message-ID: <20040104000749.GB5318@vrfy.org> (raw)
In-Reply-To: <20040103200753.GA4917@vrfy.org>
On Sun, Jan 04, 2004 at 12:42:04AM +0100, Kay Sievers wrote:
> On Sat, Jan 03, 2004 at 03:31:49PM -0800, Greg KH wrote:
> > On Sun, Jan 04, 2004 at 12:07:21AM +0100, Kay Sievers wrote:
> > > On Sat, Jan 03, 2004 at 01:48:57PM -0800, Greg KH wrote:
> > > > On Sat, Jan 03, 2004 at 09:07:53PM +0100, Kay Sievers wrote:
> > > > > While connecting my flash reader to the USB bus I get:
> > > > >
> > > > > Jan 3 20:56:58 pim udev[31673]: sleep_for_dev: looking for '/sys/class/scsi_device/54:0:0:2/dev'
> > > > > Jan 3 20:56:59 pim udev[31695]: sleep_for_dev: looking for '/sys/class/scsi_device/54:0:0:3/dev'
> > > > > Jan 3 20:56:59 pim udev[31514]: sleep_for_dev: looking for '/sys/class/scsi_host/host54/dev'
> > > > >
> > > > > Shouldn't we blacklist devices like /sys/class/scsi_device/*, /sys/class/scsi_host/* ?
> > > >
> > > > Yes we should, as we try to remove those device nodes when the devices
> > > > get removed (look for the 'trying to remove host54' messages), which
> > > > could be very dangerous.
> > > >
> > >
> > > So, here we go:
> > >
> > > Blacklist devices that we don't want to process, like:
> > > /sys/class/scsi_device/*, /sys/class/scsi_host/*,
> > > cause these devices are handled by the block device events we receive
> > > and we don't try to remove non existing nodes.
> >
> > How about this patch instead (not tested)? It removes the explicit test
> > for net class devices.
>
> Nice, looks good.
> I've tested it:
>
> Jan 4 00:38:40 pim udev[4389]: udev_hotplug: looking at '/class/scsi_device/62:0:0:0'
> Jan 4 00:38:40 pim udev[4389]: udev_hotplug: don't care about 'scsi_device' devices
>
> Jan 4 00:38:41 pim udev[4562]: udev_hotplug: looking at '/class/scsi_host/host62'
> Jan 4 00:38:41 pim udev[4562]: udev_hotplug: don't care about 'scsi_host' devices
Oh, my testing is good, but reading to the end of the debug is better :)
It should be:
if (strcmp(subsystem, subsystem_blacklist[i]) = 0) {
otherwise we skip everything.
Kay
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-04 0:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 20:07 udev - Shouldn't we blacklist some devices? Kay Sievers
2004-01-03 21:48 ` Greg KH
2004-01-03 23:07 ` Kay Sievers
2004-01-03 23:31 ` Greg KH
2004-01-03 23:42 ` Kay Sievers
2004-01-04 0:07 ` Kay Sievers [this message]
2004-01-04 8:20 ` Greg KH
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=20040104000749.GB5318@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.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 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).