linux-kernel - Re: [PATCH] sysfs: Update the name hash for an entry after changing the namespace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 4 Apr 2012 14:08:21 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Tom Goff <thomas.goff@...ing.com>
Cc:	linux-kernel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH] sysfs: Update the name hash for an entry after changing
 the namespace

On Wed, Apr 04, 2012 at 01:30:04PM -0700, Tom Goff wrote:
> On Wed, Apr 04, 2012 at 12:22:36 -0700, Greg Kroah-Hartman wrote:
> > On Wed, Apr 04, 2012 at 12:06:20PM -0700, Tom Goff wrote:
> > > This is needed to allow renaming network devices that have been moved
> > > to another network namespace.
> > > 
> > > Signed-off-by: Tom Goff <thomas.goff@...ing.com>
> > > ---
> > >  fs/sysfs/dir.c |    2 +-
> > >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > Is this a bug in 3.4-rc1 and older kernels?  If so, how old?
> > 
> > thanks,
> > 
> > greg k-h
> 
> Yes, this is a bug in 3.4-rc1.  The patch is really a change to
> d5c38b137ac8a6e3dbed13bc494d60df5b69dfc4 'sysfs: Update the name hash
> when renaming sysfs entries', committed on January 31.

Good, that patch only went into 3.4-rc1 and nothing newer, I'll queue
this up for 3.4-only, thanks for letting me know.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/