From: Kay Sievers <kay.sievers@vrfy.org>
To: Roland Dreier <rdreier@cisco.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver core: Convert '/' to '!' in dev_set_name()
Date: Sat, 10 Jan 2009 07:30:24 +0100 [thread overview]
Message-ID: <ac3eb2510901092230i5f1a37c6s8e7ef20cfaf67dc6@mail.gmail.com> (raw)
In-Reply-To: <adad4evoeu9.fsf@cisco.com>
On Sat, Jan 10, 2009 at 07:27, Roland Dreier <rdreier@cisco.com> wrote:
> Commit 3ada8b7e ("block: struct device - replace bus_id with dev_name(),
> dev_set_name()") deleted the code in register_disk() that changed a '/'
> to a '!' in the device name when registering a disk, but dev_set_name()
> does not perform this conversion.
>
> This leads to amusing problems with disks that have '/' in their names:
> for example a failure to boot with the root partition on a cciss device,
> even though the kernel says it knows about the root device:
>
> VFS: Cannot open root device "cciss/c0d0p6" or unknown-block(0,0)
> Please append a correct "root=" boot option; here are the available partitions:
> 6800 71652960 cciss/c0d0 driver: cciss
> 6802 1 cciss/c0d0p2
> 6805 2931831 cciss/c0d0p5
> 6806 34354908 cciss/c0d0p6
> 6810 71652960 cciss/c0d1 driver: cciss
>
> Fix this by adding code to change '/' to '!' in dev_set_name() to handle
> this until dev_set_name() is converted to use kobject_set_name().
Great! Thanks a lot for fixing this,
Kay
next prev parent reply other threads:[~2009-01-10 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 5:57 [PATCH] block: Fix register_disk() when name has '/' in it Roland Dreier
2009-01-10 6:08 ` Kay Sievers
2009-01-10 6:11 ` Roland Dreier
2009-01-10 6:18 ` Kay Sievers
2009-01-10 6:27 ` [PATCH] driver core: Convert '/' to '!' in dev_set_name() Roland Dreier
2009-01-10 6:30 ` Kay Sievers [this message]
2009-01-11 6:52 ` Roland Dreier
2009-01-11 7:31 ` Greg KH
2009-01-15 22:49 ` Roland Dreier
2009-01-15 22:57 ` Greg KH
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=ac3eb2510901092230i5f1a37c6s8e7ef20cfaf67dc6@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=gregkh@suse.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.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®