From: Artem Bityutskiy <dedekind@yandex.ru>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Serge Hallyn <serue@us.ibm.com>, Tony Luck <tony.luck@intel.com>,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH 01/59] CRED: Wrap task credential accesses in the IA64
Date: Wed, 27 Aug 2008 14:55:22 +0000 [thread overview]
Message-ID: <48B56ADA.8010808@yandex.ru> (raw)
In-Reply-To: <20080827134547.19980.38813.stgit@warthog.procyon.org.uk>
David Howells wrote:
> Wrap access to task credentials so that they can be separated more easily from
> the task_struct during the introduction of COW creds.
>
> Change most current->(|e|s|fs)[ug]id to current_(|e|s|fs)[ug]id().
>
> Change some task->e?[ug]id to task_e?[ug]id(). In some places it makes more
> sense to use RCU directly rather than a convenient wrapper; these will be
> addressed by later patches.
>
> Signed-off-by: David Howells <dhowells@redhat.com>
> Reviewed-by: James Morris <jmorris@namei.org>
> Acked-by: Serge Hallyn <serue@us.ibm.com>
> Cc: Tony Luck <tony.luck@intel.com>
> Cc: linux-ia64@vger.kernel.org
Fine with me. Do you want us to put this patch to ubifs-2.6.git or you
prefer to make it go together with the rest of the CRED patches?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2008-08-27 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080827134541.19980.61042.stgit@warthog.procyon.org.uk>
2008-08-27 13:45 ` [PATCH 01/59] CRED: Wrap task credential accesses in the IA64 arch David Howells
2008-08-27 14:55 ` Artem Bityutskiy [this message]
2008-08-27 15:24 ` David Howells
2008-08-27 23:21 ` [PATCH 01/59] CRED: Wrap task credential accesses in the IA64 Stephen Rothwell
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=48B56ADA.8010808@yandex.ru \
--to=dedekind@yandex.ru \
--cc=dhowells@redhat.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox