From: Joe Perches <joe@perches.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Saurabh Sengar <saurabh.truth@gmail.com>,
eparis@redhat.com, linux-audit@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] audit: removing unused variable
Date: Wed, 28 Oct 2015 15:12:53 -0700 [thread overview]
Message-ID: <1446070373.2757.147.camel@perches.com> (raw)
In-Reply-To: <7739343.KgmgksQykM@sifl>
On Wed, 2015-10-28 at 16:35 -0400, Paul Moore wrote:
> On Wednesday, October 28, 2015 09:40:34 AM Saurabh Sengar wrote:
> > variavle rc in not required as it is just used for unchanged for return,
> > and return is always 0 in the function.
[]
> Thanks, applied with some spelling corrections to the description.
As the return value is never actually tested,
it seems better to make it a void function,
> > diff --git a/kernel/audit.c b/kernel/audit.c
[]
> > @@ -686,23 +686,22 @@ static int audit_netlink_ok(struct sk_buff *skb, u16
> > msg_type)
> >
> > static int audit_log_common_recv_msg(struct audit_buffer **ab, u16
> > msg_type) {
> > - int rc = 0;
> > uid_t uid = from_kuid(&init_user_ns, current_uid());
> > pid_t pid = task_tgid_nr(current);
> >
> > if (!audit_enabled && msg_type != AUDIT_USER_AVC) {
> > *ab = NULL;
> > - return rc;
> > + return 0;
> > }
> >
> > *ab = audit_log_start(NULL, GFP_KERNEL, msg_type);
> > if (unlikely(!*ab))
> > - return rc;
> > + return 0;
> > audit_log_format(*ab, "pid=%d uid=%u", pid, uid);
> > audit_log_session_info(*ab);
> > audit_log_task_context(*ab);
> >
> > - return rc;
> > + return 0;
> > }
> >
> > int is_audit_feature_set(int i)
>
next prev parent reply other threads:[~2015-10-28 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 4:10 [PATCH] audit: removing unused variable Saurabh Sengar
2015-10-28 20:35 ` Paul Moore
2015-10-28 22:12 ` Joe Perches [this message]
2015-10-29 14:06 ` Paul Moore
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=1446070373.2757.147.camel@perches.com \
--to=joe@perches.com \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=saurabh.truth@gmail.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