All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: David Howells <dhowells@redhat.com>
Cc: jmorris@namei.org, serue@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CRED: Fixup credentials build breakage
Date: Wed, 13 Aug 2008 07:26:06 -0600	[thread overview]
Message-ID: <20080813132606.GA10529@ldl.fc.hp.com> (raw)
In-Reply-To: <15419.1218626809@redhat.com>

* David Howells <dhowells@redhat.com>:
> Alex Chiang <achiang@hp.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


      reply	other threads:[~2008-08-13 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13  5:34 [PATCH] CRED: Fixup credentials build breakage Alex Chiang
2008-08-13 11:26 ` David Howells
2008-08-13 13:26   ` Alex Chiang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080813132606.GA10529@ldl.fc.hp.com \
    --to=achiang@hp.com \
    --cc=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.