From: Steffen Klassert <steffen.klassert@secunet.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: <jmlatten@linux.vnet.ibm.com>, <herbert@gondor.apana.org.au>,
<davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] xfrm: Remove useless secid field from xfrm_audit.
Date: Thu, 24 Apr 2014 12:55:05 +0200 [thread overview]
Message-ID: <20140424105505.GU32371@secunet.com> (raw)
In-Reply-To: <201404222148.JCD13571.QLFFJMtHOSFVOO@I-love.SAKURA.ne.jp>
On Tue, Apr 22, 2014 at 09:48:30PM +0900, Tetsuo Handa wrote:
>
> Wow. I raced with your commit. I was making V2 patch because it seemed
> to me that
>
> struct xfrm_audit {
> u32 secid;
> kuid_t loginuid;
> unsigned int sessionid;
> };
>
> can be packed as "bool" and replace "kuid_t auid, unsigned int ses, u32 secid"
> arguments with single bool argument.
>
> I subtracted your commit from my V2 patch. Would you check below one?
> ----------
> >From 225dcb015abbad724cb4b6bda837e0132eb7b2dc Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Date: Tue, 22 Apr 2014 21:34:34 +0900
> Subject: [PATCH] xfrm: Remove useless xfrm_audit struct.
>
> Commit f1370cc4 "xfrm: Remove useless secid field from xfrm_audit." changed
> "struct xfrm_audit" to have either
> { audit_get_loginuid(current) / audit_get_sessionid(current) } or
> { INVALID_UID / -1 } pair.
>
> This means that we can represent "struct xfrm_audit" as "bool".
> This patch replaces "struct xfrm_audit" argument with "bool".
>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Looks good, also applied.
Thanks a lot!
prev parent reply other threads:[~2014-04-24 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 16:00 [PATCH] xfrm: Remove useless secid field from xfrm_audit Tetsuo Handa
2014-04-22 12:02 ` Steffen Klassert
2014-04-22 12:48 ` Tetsuo Handa
2014-04-24 10:55 ` Steffen Klassert [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=20140424105505.GU32371@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jmlatten@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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;
as well as URLs for NNTP newsgroup(s).