From: Paul Moore <paul@paul-moore.com>
To: stable@vger.kernel.org
Cc: Richard Guy Briggs <rgb@redhat.com>,
linux-audit@redhat.com, linux-kernel@vger.kernel.org,
sgrubb@redhat.com
Subject: Re: [PATCH][STABLE] audit: correct AUDIT_GET_FEATURE return message type
Date: Wed, 29 Oct 2014 09:52:39 -0400 [thread overview]
Message-ID: <6874821.5ihWZEPEQR@sifl> (raw)
In-Reply-To: <20141029133506.GN26201@madcap2.tricolour.ca>
On Wednesday, October 29, 2014 09:35:06 AM Richard Guy Briggs wrote:
> When an AUDIT_GET_FEATURE message is sent from userspace to the kernel, it
> should reply with a message tagged as an AUDIT_GET_FEATURE type with a
> struct audit_feature. The current reply is a message tagged as an
> AUDIT_GET type with a struct audit_feature.
>
> This appears to have been a cut-and-paste-eo in commit b0fed40.
>
> Reported-by: Steve Grubb <sgrubb@redhat.com>
> Cc: stable@vger.kernel.org # v3.13-rc1
> Signed-off-by: Richard Guy Briggs <rgb@redhat.com>
> ---
> kernel/audit.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Acked-by: Paul Moore <paul@paul-moore.com>
> diff --git a/kernel/audit.c b/kernel/audit.c
> index d20f00f..3a80abb 100644
> --- a/kernel/audit.c
> +++ b/kernel/audit.c
> @@ -724,7 +724,7 @@ static int audit_get_feature(struct sk_buff *skb)
>
> seq = nlmsg_hdr(skb)->nlmsg_seq;
>
> - audit_send_reply(skb, seq, AUDIT_GET, 0, 0, &af, sizeof(af));
> + audit_send_reply(skb, seq, AUDIT_GET_FEATURE, 0, 0, &af, sizeof(af));
>
> return 0;
> }
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2014-10-29 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 13:35 [PATCH][STABLE] audit: correct AUDIT_GET_FEATURE return message type Richard Guy Briggs
2014-10-29 13:52 ` Paul Moore [this message]
2014-10-29 15:50 ` Greg KH
2014-10-29 16:29 ` Richard Guy Briggs
2014-10-29 18:56 ` Richard Guy Briggs
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=6874821.5ihWZEPEQR@sifl \
--to=paul@paul-moore.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgb@redhat.com \
--cc=sgrubb@redhat.com \
--cc=stable@vger.kernel.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