From: Paul Moore <paul.moore@hp.com>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: davem@davemloft.net, jmorris@namei.org, netdev@vger.kernel.org,
linux-audit@redhat.com
Subject: Re: [PATCH net-2.6/stable] [XFRM] AUDIT: Fix flowlabel text format.
Date: Mon, 28 Apr 2008 10:14:44 -0400 [thread overview]
Message-ID: <200804281014.44318.paul.moore@hp.com> (raw)
In-Reply-To: <20080427.125437.59237838.yoshfuji@linux-ipv6.org>
On Saturday 26 April 2008 11:54:37 pm YOSHIFUJI Hideaki / 吉藤英明 wrote:
> [XFRM] AUDIT: Fix flowlabel text format ambibuity.
>
> Flowlabel text format was not correct and thus ambiguous.
> For example, 0x00123 or 0x01203 are formatted as 0x123.
> This is not what audit tools want.
>
> Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Thanks for catching this.
I'm CC'ing the audit list on this because they get nervous when people
start changing the audit records. However, I'll ack this patch because
I think the previous behavior was incorrect and this should be
considered a bugfix.
Acked-by: Paul Moore <paul.moore@hp.com>
> ---
> diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
> index 5dcc10b..fac27ce 100644
> --- a/net/xfrm/xfrm_state.c
> +++ b/net/xfrm/xfrm_state.c
> @@ -2112,7 +2112,7 @@ static void xfrm_audit_helper_pktinfo(struct
> sk_buff *skb, u16 family, iph6 = ipv6_hdr(skb);
> audit_log_format(audit_buf,
> " src=" NIP6_FMT " dst=" NIP6_FMT
> - " flowlbl=0x%x%x%x",
> + " flowlbl=0x%x%02x%02x",
> NIP6(iph6->saddr),
> NIP6(iph6->daddr),
> iph6->flow_lbl[0] & 0x0f,
--
paul moore
linux @ hp
next prev parent reply other threads:[~2008-04-28 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 3:24 [PATCH net-2.6/stable] [XFRM] AUDIT: Fix flowlabel text format YOSHIFUJI Hideaki / 吉藤英明
2008-04-27 3:25 ` David Miller
2008-04-27 3:54 ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-27 5:25 ` David Miller
2008-04-27 23:09 ` James Morris
2008-04-28 14:14 ` Paul Moore [this message]
2008-04-28 14:35 ` Eric Paris
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=200804281014.44318.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=linux-audit@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/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).