From: Chris Friesen <chris.friesen@genband.com>
To: LKML <linux-kernel@vger.kernel.org>, linux-hotplug@vger.kernel.org
Subject: Re: "udevadm info --attribute-walk --path=/block/sda" doesn't show parents
Date: Wed, 18 Apr 2012 21:46:00 +0000 [thread overview]
Message-ID: <4F8F3618.3070706@genband.com> (raw)
In-Reply-To: <4F8F3563.9020701@genband.com>
On 04/18/2012 03:42 PM, Chris Friesen wrote:
>
> I have a 2.6.34.10-based kernel with udev-161 (also tested with udevadm from udev-173).
>
> When I run "udevadm info --attribute-walk --path=/block/sda" it just shows the device
> itself, and doesn't walk the whole chain showing the parents.
>
> Is there anything I can do, or am I caught with a kernel that isn't properly supported?
> I'm not subscribed to the hotplug list, so cc'ing me would be appreciated.
>
>
> I don't know what's causing the problem, but I find it suspicious that /sys/block/sda
> is a directory rather than a symlink like it is on my 2.6.35.14 laptop. I'm poking
> around in the udevadm code now.
>
>
> Some possibly-useful information:
I forgot to include this....this might be useful as well:
root@typhoon-base-unit0:/root> udevadm info -q path -n /dev/sda
/block/sda
For comparison, on my 2.6.35.14 laptop I get:
[cfriesen@blah log]$ udevadm info -q path -n /dev/sda
/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
WARNING: multiple messages have this Message-ID (diff)
From: Chris Friesen <chris.friesen@genband.com>
To: LKML <linux-kernel@vger.kernel.org>, linux-hotplug@vger.kernel.org
Subject: Re: "udevadm info --attribute-walk --path=/block/sda" doesn't show parents
Date: Wed, 18 Apr 2012 15:46:00 -0600 [thread overview]
Message-ID: <4F8F3618.3070706@genband.com> (raw)
In-Reply-To: <4F8F3563.9020701@genband.com>
On 04/18/2012 03:42 PM, Chris Friesen wrote:
>
> I have a 2.6.34.10-based kernel with udev-161 (also tested with udevadm from udev-173).
>
> When I run "udevadm info --attribute-walk --path=/block/sda" it just shows the device
> itself, and doesn't walk the whole chain showing the parents.
>
> Is there anything I can do, or am I caught with a kernel that isn't properly supported?
> I'm not subscribed to the hotplug list, so cc'ing me would be appreciated.
>
>
> I don't know what's causing the problem, but I find it suspicious that /sys/block/sda
> is a directory rather than a symlink like it is on my 2.6.35.14 laptop. I'm poking
> around in the udevadm code now.
>
>
> Some possibly-useful information:
I forgot to include this....this might be useful as well:
root@typhoon-base-unit0:/root> udevadm info -q path -n /dev/sda
/block/sda
For comparison, on my 2.6.35.14 laptop I get:
[cfriesen@blah log]$ udevadm info -q path -n /dev/sda
/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
next prev parent reply other threads:[~2012-04-18 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 21:42 "udevadm info --attribute-walk --path=/block/sda" doesn't show parents Chris Friesen
2012-04-18 21:42 ` Chris Friesen
2012-04-18 21:46 ` Chris Friesen [this message]
2012-04-18 21:46 ` Chris Friesen
2012-04-18 22:13 ` Chris Friesen
2012-04-18 22:13 ` Chris Friesen
2012-04-18 22:41 ` Kay Sievers
2012-04-18 22:41 ` Kay Sievers
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=4F8F3618.3070706@genband.com \
--to=chris.friesen@genband.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.