Bug 431 - mdev should not remove "original" device node if rename operation is in effect
Summary: mdev should not remove "original" device node if rename operation is in effect
Status: RESOLVED FIXED
Alias: None
Product: Busybox
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.14.x
Hardware: PC Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks: 429
  Show dependency treegraph
 
Reported: 2009-07-02 09:09 UTC by Michael Tokarev
Modified: 2009-07-02 11:42 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Tokarev 2009-07-02 09:09:37 UTC
When mdev.conf specifies that a given node should be renamed, mdev deletes the "original" name in both add and remove events.  This is wrong, since rename operation is here for a reason, for example in order to resolve conflict of lpN naming (when it will die, finally? :)

Basically, we should construct device_name right from the beginning (instead of using alias), and do everything with it only, and optionally use aliaslink for symlinking.  No unlink(wrong_device_name) and no rename().
Comment 1 Denys Vlasenko 2009-07-02 11:09:17 UTC
This should be fixed in currect git. Can you confirm that current git works for you?
Comment 2 Michael Tokarev 2009-07-02 11:42:02 UTC
Aha.  There was no bug# for this and it's fixed in 1.14next.  Yes it's really fixed in there - pulled and verified.  Commit 2f86ca135069e457bb16ab9e062a10e0775717a6.  Thanks!