[Bug 568048] New: dmsetup info/dm_task_get_name returns invalid entry
http://bugzilla.novell.com/show_bug.cgi?id=568048 http://bugzilla.novell.com/show_bug.cgi?id=568048#c0 Summary: dmsetup info/dm_task_get_name returns invalid entry Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: xwhu@novell.com ReportedBy: puzel@novell.com QAContact: qa@suse.de Found By: Development Blocker: --- dmsetup info -c -j $major -m $minor returns info about device even when the device with $major/$minor is not a dm-device. I've created dm-crypt target with cryptosetup and a loop device: foxbat:~ # ls -l /dev/mapper/* crw-rw---- 1 root root 10, 60 10. pro 14.18 /dev/mapper/control brw-r----- 1 root disk 253, 0 31. pro 12.35 /dev/mapper/test foxbat:~ # ls -l /dev/loop* brw-rw---- 1 root disk 7, 0 30. pro 15.25 /dev/loop0 brw-rw---- 1 root disk 7, 1 10. pro 14.18 /dev/loop1 brw-rw---- 1 root disk 7, 2 10. pro 14.18 /dev/loop2 brw-rw---- 1 root disk 7, 3 10. pro 14.18 /dev/loop3 brw-rw---- 1 root disk 7, 4 10. pro 14.18 /dev/loop4 brw-rw---- 1 root disk 7, 5 10. pro 14.18 /dev/loop5 brw-rw---- 1 root disk 7, 6 10. pro 14.18 /dev/loop6 brw-rw---- 1 root disk 7, 7 10. pro 14.18 /dev/loop7 foxbat:~ # losetup -a /dev/loop0: [0803]:392301 (/tmp/loopfile) foxbat:~ # dmsetup info Name: test State: ACTIVE Read Ahead: 256 Tables present: LIVE Open count: 0 Event number: 0 Major, minor: 253, 0 Number of targets: 1 Then, running dmsetup info with minor and major numbers belonging to the loop device gives information about the _dm_ device, but it should IMHO output nothing: foxbat:~ # dmsetup info -c -j 7 -m 0 Name Maj Min Stat Open Targ Event UUID test 253 0 L--w 0 1 0 This did _not_ happen in 11.1. Moreover, it is not related only to dmsetup tool, but something is wrong with libdevmapper (see bug #552596). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=568048
http://bugzilla.novell.com/show_bug.cgi?id=568048#c1
Xinwei Hu
http://bugzilla.novell.com/show_bug.cgi?id=568048
http://bugzilla.novell.com/show_bug.cgi?id=568048#c2
Petr Uzel
http://bugzilla.novell.com/show_bug.cgi?id=568048
http://bugzilla.novell.com/show_bug.cgi?id=568048#c3
Xinwei Hu
Hmm, that explains it, thanks. Is this SUSE specific or upstream behavior? Are The upstream introduces this issue, and has been fixed there now. you going to change that for 11.2 via maintenance update or just for Factory/SLE11-SP1? I'd like to know to properly handle bug #552596. TIA Which do you prefer ? I'm OK with both ;)
-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=568048
http://bugzilla.novell.com/show_bug.cgi?id=568048#c4
--- Comment #4 from Petr Uzel
you going to change that for 11.2 via maintenance update or just for Factory/SLE11-SP1? I'd like to know to properly handle bug #552596. TIA Which do you prefer ? I'm OK with both ;)
Well, it's your package - if it is only kpartx affected (#552596), I can fix it easily without dm update (and it should be done anyway). I've no idea whether reverting old behavior might cause any unexpected issues. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=568048
http://bugzilla.novell.com/show_bug.cgi?id=568048#c5
Xinwei Hu
(In reply to comment #3)
you going to change that for 11.2 via maintenance update or just for Factory/SLE11-SP1? I'd like to know to properly handle bug #552596. TIA Which do you prefer ? I'm OK with both ;)
Well, it's your package - if it is only kpartx affected (#552596), I can fix it easily without dm update (and it should be done anyway). I've no idea whether reverting old behavior might cause any unexpected issues.
This should only affect 11.2. And it seems to affect kpartx only. If you can fix this for kpartx, I'll leave device-mapper as it is ;) Is this OK for you ? Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=568048
http://bugzilla.novell.com/show_bug.cgi?id=568048#c6
Petr Uzel
If you can fix this for kpartx, I'll leave device-mapper as it is ;) Is this OK for you ?
Yes, let's do it this way. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=568048
http://bugzilla.novell.com/show_bug.cgi?id=568048#c7
--- Comment #7 from Hannes Reinecke
http://bugzilla.novell.com/show_bug.cgi?id=568048
http://bugzilla.novell.com/show_bug.cgi?id=568048#c8
Xinwei Hu
participants (1)
-
bugzilla_noreply＠novell.com