From: Andrew Morton <akpm@linux-foundation.org>
To: Ryan Mallon <rmallon@gmail.com>
Cc: Mark Salter <msalter@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"trivial@kernel.org" <trivial@kernel.org>
Subject: Re: [PATCH][REPOST] Check maxlen on strnlen_user usage
Date: Wed, 7 Sep 2011 17:06:21 -0700 [thread overview]
Message-ID: <20110907170621.389b1314.akpm@linux-foundation.org> (raw)
In-Reply-To: <4E68042A.1050406@gmail.com>
On Thu, 08 Sep 2011 09:54:18 +1000
Ryan Mallon <rmallon@gmail.com> wrote:
> strnlen_user returns the length of the string including the nul
> terminator. In the case where maxlen is reached strnlen_user returns
> maxlen + 1. Most callsites already check for this condition. Fix the
> call to strnlen_user in fs/exec.c to check for the maxlen case.
>
> diff --git a/fs/exec.c b/fs/exec.c
> index 25dcbe5..e19588c 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -481,7 +481,7 @@ static int copy_strings(int argc, struct
> user_arg_ptr argv,
> goto out;
>
> len = strnlen_user(str, MAX_ARG_STRLEN);
> - if (!len)
> + if (!len || len> MAX_ARG_STRLEN)
> goto out;
>
> ret = -E2BIG;
The following call to vald_arg_len() already does this?
This change will cause copy_strings() to incorrectly return -EFAULT,
rather than -E2BIG.
Your email client is wordwrapping and space-stuffing the patches, btw.
next prev parent reply other threads:[~2011-09-08 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 23:54 [PATCH][REPOST] Check maxlen on strnlen_user usage Ryan Mallon
2011-09-08 0:06 ` Andrew Morton [this message]
2011-09-08 0:20 ` Ryan Mallon
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=20110907170621.389b1314.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msalter@redhat.com \
--cc=rmallon@gmail.com \
--cc=trivial@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).