linux-kernel - Re: Resolved merge conflicts in next-creds

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:	Tue, 12 Aug 2008 21:19:04 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	David Howells <dhowells@...hat.com>
Cc:	James Morris <jmorris@...ei.org>, linux-kernel@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>,
	Steve French <sfrench@...ibm.com>
Subject: Re: Resolved merge conflicts in next-creds

Hi David,

On Tue, 12 Aug 2008 10:27:08 +0100 David Howells <dhowells@...hat.com> wrote:
>
> Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
> > The important thing (and what is different in what I have proposed) is
> > that what you are asking Linus to take here has zero impact (i.e. you just
> > add a header file that noone uses and whose contents are clearly noops)
> > and then it is very obvious that when people start to use it, the changes
> > really cannot introduce a regression.
> 
> Actually, you do have to modify XFS too.  It declares current_fsuid(),
> current_fsgid() and struct cred within itself.  The first two just require
> some simple renames, and the third just requires using my struct cred instead
> when it appears.

One step at a time ... the rename is clearly necessary, but adding
"struct cred" can wait.  We may not be able to get all the conflicts
solved by adding stuff to Linus' tree early.  My aim is just to reduce my
pain level.  :-)

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped