From: Eric Paris <eparis@redhat.com>
To: zhangxiliang <zhangxiliang@cn.fujitsu.com>
Cc: sgrubb@redhat.com, viro@zeniv.linux.org.uk,
Linux Audit <linux-audit@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix the bug of using AUDIT_STATUS_RATE_LIMIT when set fail, no error output.
Date: Wed, 30 Jul 2008 23:15:50 -0400 [thread overview]
Message-ID: <1217474150.2902.76.camel@localhost.localdomain> (raw)
In-Reply-To: <48911F47.50606@cn.fujitsu.com>
On Thu, 2008-07-31 at 10:11 +0800, zhangxiliang wrote:
> When the "status_get->mask" is "AUDIT_STATUS_RATE_LIMIT || AUDIT_STATUS_BACKLOG_LIMIT".
> If "audit_set_rate_limit" fails and "audit_set_backlog_limit" succeeds, the "err" value will be greater than or equal to 0. It will miss the failure of rate set.
>
> Signed-off-by: Zhang Xiliang <zhangxiliang@cn.fujitsu.com>
man, it gives me the heebee jeebies with the coding style but it follows
everything else
Acked-by: Eric Paris <eparis@redhat.com>
> ---
> kernel/audit.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/kernel/audit.c b/kernel/audit.c
> index e092f1c..38a4080 100644
> --- a/kernel/audit.c
> +++ b/kernel/audit.c
> @@ -725,9 +725,11 @@ static int audit_receive_msg(struct sk_buff *skb, struct nlmsghdr *nlh)
> audit_pid = new_pid;
> audit_nlk_pid = NETLINK_CB(skb).pid;
> }
> - if (status_get->mask & AUDIT_STATUS_RATE_LIMIT)
> + if (status_get->mask & AUDIT_STATUS_RATE_LIMIT) {
> err = audit_set_rate_limit(status_get->rate_limit,
> loginuid, sessionid, sid);
> + if (err < 0) return err;
> + }
> if (status_get->mask & AUDIT_STATUS_BACKLOG_LIMIT)
> err = audit_set_backlog_limit(status_get->backlog_limit,
> loginuid, sessionid, sid);
> --
> 1.5.4.2
>
>
next prev parent reply other threads:[~2008-07-31 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 2:11 [PATCH] Fix the bug of using AUDIT_STATUS_RATE_LIMIT when set fail, no error output zhangxiliang
2008-07-31 3:15 ` Eric Paris [this message]
2008-07-31 16:04 ` Al Viro
2008-07-31 21:59 ` Andrew Morton
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=1217474150.2902.76.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sgrubb@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zhangxiliang@cn.fujitsu.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