linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev - Shouldn't we blacklist some devices?
Date: Sat, 03 Jan 2004 23:07:21 +0000	[thread overview]
Message-ID: <20040103230721.GA5235@vrfy.org> (raw)
In-Reply-To: <20040103200753.GA4917@vrfy.org>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

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.


thanks,
Kay

[-- Attachment #2: 01-blacklist-for-devices.diff --]
[-- Type: text/plain, Size: 802 bytes --]

diff -Nru a/udev.c b/udev.c
--- a/udev.c	Sat Jan  3 23:58:38 2004
+++ b/udev.c	Sat Jan  3 23:58:38 2004
@@ -139,12 +139,19 @@
 	return retval;
 }
 
+static char *dev_path_blacklist[] = {
+	"class/scsi_host",
+	"class/scsi_device",
+	""
+};
+
 static inline int udev_hotplug(int argc, char **argv)
 {
 	char *action;
 	char *devpath;
 	char *subsystem;
 	int retval = -EINVAL;
+	int i;
 
 	subsystem = argv[1];
 
@@ -160,6 +167,16 @@
 	    !strstr(devpath, "block")) {
 		dbg("not a block or class device");
 		goto exit;
+	}
+
+	/* skip blacklisted path */
+	i = 0;
+	while (dev_path_blacklist[i][0] != '\0') {
+		if (strstr(devpath, dev_path_blacklist[i])) {
+			dbg("device with path '%s' is blacklisted", devpath);
+			goto exit;
+		}
+		i++;
 	}
 
 	/* but we don't care about net class devices */

  parent reply	other threads:[~2004-01-03 23: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 [this message]
2004-01-03 23:31 ` Greg KH
2004-01-03 23:42 ` Kay Sievers
2004-01-04  0:07 ` Kay Sievers
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=20040103230721.GA5235@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).