Re: Bug#561279: udev: Crash location and first-level cause

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Dec 24, 2009 at 20:26, Marco d'Itri <md@xxxxxxxx> wrote:
> (gdb) run
> Starting program: /usr/src/udev-149/build-deb/udev/udevadm info --root --query name --path /sys/block/md4
>
> Program received signal SIGSEGV, Segmentation fault.
...
> It appears that udev_device_get_devnode() is returning NULL, which
> udevadm_info() isn???t expecting. I don???t know why the device node is
> NULL though...

No idea why the md device seems not to have information about a device
node. I guess there is some timing issue left to resolve.

But there was an obvious bug in the handling of --root for devices
without a known device node. Udevadm in upstream udev git is fixed now
not to segfault here.

Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux DVB]     [Asterisk Internet PBX]     [DCCP]     [Netdev]     [X.org]     [Util Linux NG]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux