From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Cc: "Kay Sievers" <kay.sievers@vrfy.org>, "Greg KH" <greg@kroah.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@osdl.org>,
"Martin Schwidefsky" <schwidefsky@de.ibm.com>
Subject: Re: [Patch -mm 2/5] driver core: Introduce device_move(): move a device to a new parent.
Date: Wed, 15 Nov 2006 18:23:11 +0100 [thread overview]
Message-ID: <20061115182311.70821c97@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <d120d5000611150844s16980cf3r2fca9a71d439cbed@mail.gmail.com>
On Wed, 15 Nov 2006 11:44:36 -0500,
"Dmitry Torokhov" <dmitry.torokhov@gmail.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@de.ibm.com
next prev parent reply other threads:[~2006-11-15 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 10:32 Cornelia Huck
2006-11-15 6:50 ` Greg KH
2006-11-15 7:28 ` Cornelia Huck
2006-11-15 8:44 ` Kay Sievers
2006-11-15 9:24 ` Cornelia Huck
2006-11-15 9:31 ` Kay Sievers
2006-11-15 10:11 ` Cornelia Huck
2006-11-15 16:44 ` Dmitry Torokhov
2006-11-15 17:23 ` Cornelia Huck [this message]
2006-11-15 17:39 ` Cornelia Huck
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=20061115182311.70821c97@gondolin.boeblingen.de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=akpm@osdl.org \
--cc=dmitry.torokhov@gmail.com \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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
all inboxes | Powered by JetHome®