From: Eric W. Biederman <hidden> Date: 2012-01-31 14:37:48
This fixes a bug introduced with sysfs name hashes where renaming a
network device appears to succeed but silently makes the sysfs files for
that network device inaccessible.
In at least one configuration this bug has stopped networking from
coming up during boot.
Signed-off-by: Eric W. Biederman <redacted>
---
fs/sysfs/dir.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
@@ -872,6 +872,7 @@ int sysfs_rename(struct sysfs_dirent *sd,dup_name=sd->s_name;sd->s_name=new_name;+sd->s_hash=sysfs_name_hash(sd->s_ns,sd->s_name);}/* Move to the appropriate place in the appropriate directories rbtree. */
This fixes a bug introduced with sysfs name hashes where renaming a
network device appears to succeed but silently makes the sysfs files for
that network device inaccessible.
In at least one configuration this bug has stopped networking from
coming up during boot.
Signed-off-by: Eric W. Biederman <redacted>
It works for me. Thanks.
Tested-by: Jiri Slaby <redacted>
@@ -872,6 +872,7 @@ int sysfs_rename(struct sysfs_dirent *sd,dup_name=sd->s_name;sd->s_name=new_name;+sd->s_hash=sysfs_name_hash(sd->s_ns,sd->s_name);}/* Move to the appropriate place in the appropriate directories rbtree. */
On Tue, Jan 31, 2012 at 06:40:26AM -0800, Eric W. Biederman wrote:
This fixes a bug introduced with sysfs name hashes where renaming a
network device appears to succeed but silently makes the sysfs files for
that network device inaccessible.
In at least one configuration this bug has stopped networking from
coming up during boot.
Signed-off-by: Eric W. Biederman <redacted>
---
fs/sysfs/dir.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
Thanks for this, I'll queue it up later today.
greg k-h