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]

Message-Id: <1163583119.4244.6.camel@pim.off.vrfy.org>
Date:	Wed, 15 Nov 2006 10:31:59 +0100
From:	Kay Sievers <kay.sievers@...y.org>
To:	Cornelia Huck <cornelia.huck@...ibm.com>
Cc:	Greg KH <greg@...ah.com>,
	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 Wed, 2006-11-15 at 10:24 +0100, Cornelia Huck wrote:
> On Wed, 15 Nov 2006 09:44:33 +0100,
> "Kay Sievers" <kay.sievers@...y.org> wrote:
> 
> > Udev and HAL, both will need an event for the moving, with the old
> > DEVPATH value in the environment. We want something like a "rename" or
> > "move" event. Without that, weird things will happen in userspace,
> > because the devpath is used as the key to the device during the whole
> > device lifetime. The only weird exception today is the netif rename
> > case, which is already handled by special code in udev.
> 
> Something like below (completely untested as my test box is currently
> inaccessible)?

We need the old DEVPATH in the environment (or something similar),
otherwise we can't connect the event with the new device location to the
current device. :)

> Wouldn't we need something similar for kobject_rename()
> as well?

Maybe kobject_rename() can go, if we have a move function which can be
used. In any case, the events should look identical to userspace, yes.

Thanks,
Kay

-
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/