From: Eric Paris <eparis@redhat.com>
To: Chen Gang <gang.chen@asianux.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] kernel: audit: beautify code, for extern function, better to check its parameters by itself
Date: Wed, 10 Apr 2013 13:31:03 -0400 (EDT) [thread overview]
Message-ID: <1216477171.11118824.1365615063121.JavaMail.root@redhat.com> (raw)
In-Reply-To: <5161347B.8090604@asianux.com>
----- Original Message -----
>
> __audit_socketcall is an extern function.
> better to check its parameters by itself.
>
> also can return error code, when fail (find invalid parameters).
> also use macro instead of real hard code number
> also give related comments for it.
>
> Signed-off-by: Chen Gang <gang.chen@asianux.com>
> ---
> include/linux/audit.h | 12 ++++++++----
> kernel/auditsc.c | 9 ++++++---
> net/socket.c | 6 ++++--
> 3 files changed, 18 insertions(+), 9 deletions(-)
>
> diff --git a/include/linux/audit.h b/include/linux/audit.h
> @@ -354,7 +358,7 @@ static inline int audit_bprm(struct linux_binprm *bprm)
> {
> return 0;
> }
> -static inline void audit_socketcall(int nargs, unsigned long *args)
> +static inline int audit_socketcall(int nargs, unsigned long *args)
> { }
> static inline void audit_fd_pair(int fd1, int fd2)
> { }
This now returns a value but you forgot to return a value. Thus this would not even build... I fixed it up myself.
-Eric
next prev parent reply other threads:[~2013-04-10 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 8:55 [PATCH] kernel: audit: beautify code, for extern function, better to check its parameters by itself Chen Gang
2013-04-10 17:31 ` Eric Paris [this message]
2013-04-11 1:03 ` Chen Gang
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=1216477171.11118824.1365615063121.JavaMail.root@redhat.com \
--to=eparis@redhat.com \
--cc=davem@davemloft.net \
--cc=gang.chen@asianux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).