linux-kernel - Re: [Patch -mm 2/5] driver core: Introduce device

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 15 Nov 2006 08:28:56 +0100
From:	Cornelia Huck <cornelia.huck@...ibm.com>
To:	Greg KH <greg@...ah.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>,
	Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: Re: [Patch -mm 2/5] driver core: Introduce device_move(): move a
 device to a new parent.

On Tue, 14 Nov 2006 22:50:52 -0800,
Greg KH <greg@...ah.com> wrote:

> On Tue, Nov 14, 2006 at 11:32:08AM +0100, Cornelia Huck wrote:
> > From: Cornelia Huck <cornelia.huck@...ibm.com>
> > 
> > Provide a function device_move() to move a device to a new parent device. Add
> > auxilliary functions kobject_move() and sysfs_move_dir().
> 
> At first glance, this looks sane, but for the kobject_move function, we
> are not notifying userspace that something has changed here.
> 
> Is that ok?
> 
> How will udev and HAL handle something like this without being told
> about it?  When the device eventually goes away, I think they will be
> very confused.

Hm. I don't think we want to trigger udev with some remove/add events
(especially since it is still the same device, it just has been moved
around). A change event doesn't sound quite right either. But I guess
we need to do something, at least to make HAL happy since it remembers
the path in sysfs (although I seem to remember a HAL patch that got rid
of it?)

-- 
Cornelia Huck
Linux for zSeries Developer
Tel.: +49-7031-16-4837, Mail: cornelia.huck@...ibm.com
-
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/