[Bug 235244] New: udev keeps increasing devicenames without reason or need
https://bugzilla.novell.com/show_bug.cgi?id=235244 Summary: udev keeps increasing devicenames without reason or need Product: openSUSE 10.2 Version: RC 5 Platform: i586 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Hotplug AssignedTo: ihno@novell.com ReportedBy: dieter.jurzitza@t-online.de QAContact: qa@suse.de When using the ralink rt61 driver with a Digitus Network card, udev keeps increasing the raX-interfaces at every boot. /etc/udev/rules.d/30-net_persistent_name_rules is filled with entries like: SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:0e:2e:b0:c1:9b", IMPORT="/lib/udev/rename_netiface %k ra0" SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:0e:2e:b0:c1:9b", IMPORT="/lib/udev/rename_netiface %k ra1" This is a severe bug IMHO. Such things should at least be made dependant of the MAC address. Multiple entries should never appear in this file for *identical* physical network interfaces (i. e. devices with identical MAC-Adresses, as they are definitively unique). Similar issues seem to appear when interfaces are deleted, but the corresponding entries do not get deleted out of this file consistently, leading to varying names of the interface(s). The minimum check that should be undertaken is something like a short awk test prior to rewriting this file whether the SYSFS{address} entrie would be duplicated. This issue is fixable by setting in /etc/sysconfig/network/config FORCE_PERSISTENT_NAMES=no, but I do not think this is how it is meant to be. If I can support debugging anyhow - please let me know. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235244 dieter.jurzitza@t-online.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dieter.jurzitza@t-online.de ------- Comment #1 from dieter.jurzitza@t-online.de 2007-01-17 11:59 MST ------- I (think) I found the root cause for the issues I have discovered with the ralink Wlan card (other people suffer from similar problems as can be found in the internet). Debugging yielded the following results: - "/lib/udev/rename_netiface ra0" is always called on start. This differs from the call for a "normal" ethernet card "/lib/udev/rename_netiface eth0 eth0". Please note the missing second argument in the first call example. - the further steps in the script detect a valid MACADDRESS that is written into $DEV_ID. Finally check_if_name_is_free() is being called with the name ra0 as parameter. There you read: grep -qs "^[^#].*rename_netiface %k $NEWNAME\" $RULE_FILE && return 1 A persistent rule had had been put into the rule - file /etc/udev/rules.d/30-net_persistent_names.rules during configuration of the interface via YaST (by the way, this happens for each interface that is being configured, isn't it?): SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:0e:2e:b0:c1:9b", IMPORT="/lib/udev/rename_netiface %k ra0" This appears meaningful and right. Now exactly this entry is being used, to decide, that the interface of this card should not be used, because the "grep" command above returns 1 telling the script that the ID of this card should be incremented and the call should be repeated. This must be an error. By any means this rule leads to the fact that at every boot new entries are being written into the rule file, each of them referring to the very same interface. IMHO this cannot be wanted this way. However, the scripts expects network cards that do not come with two interfacenames when calling "/lib/udev/rename_netiface", thus the behaviour of my network card appears to be a regular case. To fix this, a patch has been created. This patch does basically two things: 1.) I check whether there is an entry in the rule file pointing to exactly this mac-address with exactly this interface name. If so, I assume that everything is ok and no further action is required, the call to check_if_name_is_used() returns 0 then and the further processing terminates silently. 2.) Given this (retval 0 of check_if_name_is_used() ) the new old rule should not be appended to the rulefile. Therefore I set the variable $WRITE_RULE to "no". Please take a look into the patch attached to the bug report for further details. Some more comments: In line 143 there is an inconsistency: the line 93 sets NEWNAME = $2. In line 132 $NEWNAME is checked for "". In line 143 I see the call get_device_id "$OLDNAME" "$2" hence with $2 == $NEWNAME == "" as parameter - that seems quite meaningless and irritating, isn't it? In the comment in line 138 the bug devil had bitten someone, it should say "30-net..." instead of "60-net ...". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235244 ------- Comment #2 from dieter.jurzitza@t-online.de 2007-01-17 12:01 MST ------- Created an attachment (id=113466) --> (https://bugzilla.novell.com/attachment.cgi?id=113466&action=view) Fix for erratically reassignments of if-names See my commentary II from today. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235244 ------- Comment #3 from dieter.jurzitza@t-online.de 2007-01-19 14:28 MST ------- Hi folks, even this patch fails if you plug in more than one card (i. e. two different ralink cards), and, for some malfortune, you initially configured Card 1 to ra0, however, this one becomes ra1 and Card 2 is ra0 on boot. Then the never ending increase game starts all over again. The boot structure has issues here. Let me know if I can help. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235244 dieter.jurzitza@t-online.de changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #113466|0 |1 is obsolete| | ------- Comment #4 from dieter.jurzitza@t-online.de 2007-01-21 13:36 MST ------- Created an attachment (id=114084) --> (https://bugzilla.novell.com/attachment.cgi?id=114084&action=view) Patch for erratic behaviour of /lib/udev/rename_netiface This patch fixes the erratic behaviour I found with multiple network cards and ongoing writes into /etc/udev/rules.d/30-net_persistent_names.rules The IF with the MAC Address <ADDRESS> and the assigned device <DEVICE> gets this device if no real errors occur (like duplicate device entries). Even if the sequence of devices is inverted (ra0 becoming ra1 after a new card is added that becomes ra0 in turn), the system reassigns ra0 to that card that had had been ra0 before. Please test and give me a feedback. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235244 dieter.jurzitza@t-online.de changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ihno@novell.com |bnc-team-screening@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235244 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Comment #5 from chrubis@novell.com 2007-01-22 05:28 MST ------- *** This bug has been marked as a duplicate of bug 230213 *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235244 ihno@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Comment #6 from ihno@novell.com 2007-01-22 16:30 MST ------- Closed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com