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 18:23:11 +0100
From:	Cornelia Huck <cornelia.huck@...ibm.com>
To:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
Cc:	"Kay Sievers" <kay.sievers@...y.org>, "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, 15 Nov 2006 11:44:36 -0500,
"Dmitry Torokhov" <dmitry.torokhov@...il.com> wrote:

> Why do we need to have them at all? Devices should not "move" in the
> trees - it it moves we should just treat them as old devices going
> away and new devices appearing...

But unregistering and re-registering is exactly what we want to avoid
in our case. We have still the same ccw device, it's only now
operational via another subchannel (i. e. the topology changed, but not
the device). If we unregistered the device, we would also kill the
associated block device(s), and if it had been mounted, we go boom.
(This is what currently happens without this patchset, and it may be
triggered by a short hardware outage we'd otherwise survive without a
problem.)

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