From: Stephen Smalley <sds@tycho.nsa.gov>
To: William Roberts <bill.c.roberts@gmail.com>,
linux-audit@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, rgb@redhat.com,
viro@zeniv.linux.org.uk
Cc: William Roberts <wroberts@tresys.com>
Subject: Re: [PATCH 2/3] proc: Update get proc_pid_cmdline() to use mm.h helpers
Date: Fri, 13 Dec 2013 09:23:49 -0500 [thread overview]
Message-ID: <52AB1875.2090207@tycho.nsa.gov> (raw)
In-Reply-To: <1386018639-18916-3-git-send-email-wroberts@tresys.com>
On 12/02/2013 04:10 PM, William Roberts wrote:
> Re-factor proc_pid_cmdline() to use get_cmdline_length() and
> copy_cmdline() helpers from mm.h
>
> Signed-off-by: William Roberts <wroberts@tresys.com>
> ---
> fs/proc/base.c | 35 ++++++++++-------------------------
> 1 file changed, 10 insertions(+), 25 deletions(-)
>
> diff --git a/fs/proc/base.c b/fs/proc/base.c
> index 03c8d74..fb4eda5 100644
> --- a/fs/proc/base.c
> +++ b/fs/proc/base.c
> @@ -203,37 +203,22 @@ static int proc_root_link(struct dentry *dentry, struct path *path)
> static int proc_pid_cmdline(struct task_struct *task, char * buffer)
> {
> int res = 0;
> - unsigned int len;
> + unsigned int len = 0;
Why? You set len below before first use, so this is redundant.
> struct mm_struct *mm = get_task_mm(task);
> if (!mm)
> - goto out;
> - if (!mm->arg_end)
> - goto out_mm; /* Shh! No looking before we're done */
> + return 0;
Equivalent to goto out in the original code, so why change it? Don't
make unnecessary changes.
Also, I think the get_task_mm() ought to move into the helper (or all of
proc_pid_cmdline() should just become the helper). In what situation
will you not be calling get_task_mm() and mmput() around every call to
the helper?
>
> - len = mm->arg_end - mm->arg_start;
> -
> + len = get_cmdline_length(mm);
> + if (!len)
> + goto mm_out;
Could be moved into the helper. Not sure how the inline function helps
readability or maintainability.
> +
> + /*The caller of this allocates a page */
> if (len > PAGE_SIZE)
> len = PAGE_SIZE;
If the capping of len is handled by the caller, then pass an int to your
helper rather than an unsigned int to avoid problems later with
access_process_vm().
> -out_mm:
> +
> + res = copy_cmdline(task, mm, buffer, len);
> +mm_out:
> mmput(mm);
Odd style. If there is only one exit path, just call it out; if there
are two, keep them as out_mm and out.
> -out:
> return res;
> }
>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-12-13 14:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 21:10 [PATCH] - auditing cmdline William Roberts
2013-12-02 21:10 ` [PATCH 1/3] mm: Create utility functions for accessing a tasks commandline value William Roberts
2013-12-13 14:12 ` Stephen Smalley
2013-12-13 14:51 ` William Roberts
2013-12-13 15:04 ` Stephen Smalley
2013-12-13 15:26 ` William Roberts
2013-12-13 15:27 ` William Roberts
2013-12-02 21:10 ` [PATCH 2/3] proc: Update get proc_pid_cmdline() to use mm.h helpers William Roberts
2013-12-13 14:23 ` Stephen Smalley [this message]
2013-12-13 14:57 ` William Roberts
2013-12-02 21:10 ` [PATCH 3/3] audit: Audit proc cmdline value William Roberts
2013-12-09 15:33 ` Richard Guy Briggs
2013-12-06 15:34 ` [PATCH] - auditing cmdline William Roberts
2013-12-06 15:39 ` William Roberts
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=52AB1875.2090207@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=bill.c.roberts@gmail.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rgb@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wroberts@tresys.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