linux-kernel - Re: [PATCH] ide_scsi: allow it to be used for non CD only

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <58cb370e0611291447y36430d5bta65176eb1198cdce@mail.gmail.com>
Date:	Wed, 29 Nov 2006 23:47:04 +0100
From:	"Bartlomiej Zolnierkiewicz" <bzolnier@...il.com>
To:	Alan <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
	akpm@...l.org
Subject: Re: [PATCH] ide_scsi: allow it to be used for non CD only

On 11/29/06, Alan <alan@...rguk.ukuu.org.uk> wrote:
> On Wed, 29 Nov 2006 23:05:56 +0100
> "Bartlomiej Zolnierkiewicz" <bzolnier@...il.com> wrote:
>
> > Hi,
> >
> > Nowadays, you can dynamically change driver bound to a device using
> > sysfs and it works just fine for IDE, ie:
>
> This isn't the point of this change. The point is to do this at discovery
> time. If you do it later then many horrible things happen as the device

then "hdc=ide-cdrom" at a boot time should keep ide-scsi from
binding to hdc for all cases (builtin/modular ide-cd/ide-scsi)

> names and renames itself while udev goes boom.

Uh?  I hope that udev people are informed
about these horrible things...

/dev/hdc stays there all the time
/dev/sr? addition/removal should be handled
by udev otherwise it looks like a udev bug

> Its a small clean patch and it'll solve the problem nicely until
> drivers/ide dies.

No strong feelings here about the patch.  It is indeed a clean hack. ;)
I just wanted to point out that there are already more flexible ways
to achieve the same thing.

Bart
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/