From: Joe Perches <joe@perches.com>
To: Saurabh Sengar <saurabh.truth@gmail.com>
Cc: paul@paul-moore.com, eparis@redhat.com, linux-audit@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] audit: removing unused variable
Date: Wed, 28 Oct 2015 21:32:48 -0700 [thread overview]
Message-ID: <1446093168.2757.154.camel@perches.com> (raw)
In-Reply-To: <1446091912-6001-1-git-send-email-saurabh.truth@gmail.com>
On Thu, 2015-10-29 at 09:41 +0530, Saurabh Sengar wrote:
> variable rc is unnecessary hence removing it,
> also as the return type of function audit_log_common_recv_msg is no
> where used changing it to void.
Almost, but not quite. Keep at it.
Ideally your first attempts at kernel patching
should be done in the drivers/staging/ directory
before attempting patches outside of that path.
> diff --git a/kernel/audit.c b/kernel/audit.c
[]
> @@ -684,25 +684,24 @@ static int audit_netlink_ok(struct sk_buff *skb, u16 msg_type)
> return err;
> }
>
> -static int audit_log_common_recv_msg(struct audit_buffer **ab, u16 msg_type)
> +static void 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 ;
There's an unnecessary space before the semicolon.
This should be
return;
> }
>
> *ab = audit_log_start(NULL, GFP_KERNEL, msg_type);
> if (unlikely(!*ab))
> - return rc;
> + return ;
here too
> audit_log_format(*ab, "pid=%d uid=%u", pid, uid);
> audit_log_session_info(*ab);
> audit_log_task_context(*ab);
>
> - return rc;
> + return ;
No return statement necessary here at all
> }
>
> int is_audit_feature_set(int i)
prev parent reply other threads:[~2015-10-29 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 4:11 [PATCH v2] audit: removing unused variable Saurabh Sengar
2015-10-29 4:32 ` Joe Perches [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=1446093168.2757.154.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;
as well as URLs for NNTP newsgroup(s).