| 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
| ||
|
Message-ID: <48B7AD11.2070906@kernel.org> Date: Fri, 29 Aug 2008 10:02:25 +0200 From: Tejun Heo <tj@...nel.org> To: Kay Sievers <kay.sievers@...y.org> CC: Greg KH <greg@...ah.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 2/2] uevent: handle duplicate uevent_var keys properly Kay Sievers wrote: > Not sure if I understand that correctly. Remember, that there is a > symlink "subsystem" at each device, and udev, HAL, DeviceKit reads it. > If the uevent environment key "SUBSYSTEM" does not match the symlink > target, things will break horribly. So no device can be a member of > class "cuse" but carry a SUBSYSTEM value of a different class. > > If that is how it works, I guess that must be solved differently, by > hooking into the subsystem code and create "virtual devices" at the > original class they fake, instead of their own "cuse" class. Possibly > by making cuse a "bus", and use the cuse device as a parent for the > "real" class device. For OSS emulation, it didn't really matter. For cases where it matters, I think easier path to take would be let the userland emulation set up a directory containing pseudo files and just override DEVPATH to it. Would that work? Thanks. -- tejun -- 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/
Powered by blists - more mailing lists