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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 9 Mar 2010 12:03:19 -0800
From:	Greg KH <gregkh@...e.de>
To:	Jason Gunthorpe <jgunthorpe@...idianresearch.com>
Cc:	"David P. Quigley" <dpquigl@...ho.nsa.gov>,
	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, Mar 09, 2010 at 12:53:03PM -0700, Jason Gunthorpe wrote:
> On Tue, Mar 09, 2010 at 02:46:28PM -0500, David P. Quigley wrote:
> > 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?
> > 
> > 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.
> 
> Yes, that is correct, I was only looking up to 2.6.33-rc8, I didn't
> think to check Linus's head branch, my mistake. It looks to me like
> the changeset you pointed to was put in Linus's tree after that tag,
> so it is fixed, just not in any tagged kernel.

2.6.33 is tagged, as is 2.6.34-rc1, so it should be showing up on your
end by now :)

thanks,

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/