linux-kernel - Re: [PATCH] sysfs: Fixup broken chown tracking

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1268163988.29493.1970.camel@moss-terrapins.epoch.ncsc.mil>
Date:	Tue, 09 Mar 2010 14:46:28 -0500
From:	"David P. Quigley" <dpquigl@...ho.nsa.gov>
To:	Greg KH <gregkh@...e.de>
Cc:	Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
	linux-kernel@...r.kernel.org, James Morris <jmorris@...ei.org>,
	"Eric W. Biederman" <ebiederm@...stanetworks.com>,
	Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH] sysfs: Fixup broken chown tracking

On Tue, 2010-03-09 at 11:42 -0800, Greg KH wrote:
> On Tue, Mar 09, 2010 at 02:36:12PM -0500, David P. Quigley wrote:
> > It looks like your patch is already in the tree as commit
> > 7c0ff870d1ed287504a61ed865f3d728c757436b. We saw this problem before and
> > Eric fixed it up. I thought it was very odd that you posted this 5
> > minutes ago and it was already upstream.
> 
> Yeah, this has already been resolved, did that patch not solve the issue
> for you?
> 
> thanks,
> 
> greg k-h

I don't see how it couldn't have. The patch he submitted which he says
fixes the problem is the exact same patch that Eric submitted back in
Feb. Its possible that he is using a version of 2.6.33-rc8 that is based
off of a commit before the patch was merged since 2.6.33-rc8 was tagged
on Feb 12th and your commit date in the repo is Feb 16th.

--
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/