From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alexander E. Patrakov" Date: Thu, 20 Sep 2007 15:27:34 +0000 Subject: Re: Wrong symlink handling on rule changes Message-Id: <46F29166.8060700@ums.usu.ru> List-Id: References: <200709201716.37510.zzam@gentoo.org> In-Reply-To: <200709201716.37510.zzam@gentoo.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Matthias Schwarzott wrote: > Hi there! > Playing around with rules I stepped over a strange thing. > > I played with device-mapper rules, but the bug is about general symlink > handling. > > 1. My rules did set this: > NAME="dm-0", SYMLINK="mapper/main-slash" > That results in /dev/dm-0 being a device-node and /dev/mapper/main-slash is a > symlink to it. > > 2. Swapping NAME and SYMLINK > NAME="mapper/main-slash", SYMLINK="dm-0" > and running udevtrigger changes dm-0 to be a symlink to correct target. > BUT: It changes mapper/main-slash to be a symlink to itself. > > Calling udevtrigger a second time will correct symlink. > Is this reproducible with non-device-mapper devices? I think (but I am not sure) that the device-mapper library can poke into /dev by itself, and thus calling dmsetup from the persistent storage rules may interfere with normal udev operation here. -- Alexander E. Patrakov ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel