linux-kernel - Re: [PATCH] CRED: Fixup credentials build breakage

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]

Message-ID: <20080813132606.GA10529@ldl.fc.hp.com>
Date:	Wed, 13 Aug 2008 07:26:06 -0600
From:	Alex Chiang <achiang@...com>
To:	David Howells <dhowells@...hat.com>
Cc:	jmorris@...ei.org, serue@...ibm.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] CRED: Fixup credentials build breakage

* David Howells <dhowells@...hat.com>:
> Alex Chiang <achiang@...com> wrote:
> 
> > A recent patch titled:
> > 
> > 	CRED: Separate task security context from task_struct
> > 	
> > removed task security context from task_struct, but did not
> > update all locations to use the new struct cred that was
> > introduced.
> > 
> > The change to task_struct broke perfmon and ia32 syscalls on
> > ia64.  This patch fixes the build.
> 
> I've submitted a patch to fix this.

Thanks, clearly your patch is correct and mine was not. I was
just trying to get my build going again. I can apply yours by
hand to my own tree here to get going.

> > All things considered, I'd prefer to see this patch folded
> > into 7931c65268777ed10cab22486de149d742a1f269 so we can keep
> > bisectability. Would that be possible, given that these
> > changes are "only" in linux-next and haven't hit Linus's tree
> > yet?
> 
> Probably.  I'll have to talk to Stephen about how to do this.
> I can't maintain my patches on top of linux-next now:-/

Ok, I still think this would be a good idea, so if it's possible,
that would be great.

Thanks,

/ac

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