From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org, aaw <aaw@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] fix count(), compat_count() bounds checking
Date: Sat, 20 Sep 2008 01:06:13 +0200 [thread overview]
Message-ID: <1221865573.8359.2.camel@lappy.programming.kicks-ass.net> (raw)
In-Reply-To: <20080919155003.GB3114@redhat.com>
On Fri, 2008-09-19 at 11:50 -0400, Jason Baron wrote:
> hi,
>
> With MAX_ARG_STRINGS set to 0x7FFFFFFF, and being passed to 'count()'
> and compat_count(), it would appear that the current max bounds check
> of fs/exec.c:394:
>
> if(++i > max)
> return -E2BIG;
>
> would never trigger. Since 'i' is of type int, so values would wrap and the
> function would continue looping.
>
> Simple fix seems to be chaning ++i to i++ and checking for '>='.
>
> thanks,
>
> -Jason
Right - looks sane enough, although in practise I'm not sure we'll ever
care since I suspect we'll hit the target stack limit before this.
Ollie?
> Signed-off-by: Jason Baron <jbaron@redhat.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
>
> ---
>
> fs/compat.c | 2 +-
> fs/exec.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>
> diff --git a/fs/compat.c b/fs/compat.c
> index 3d4d57a..2c68dd7 100644
> --- a/fs/compat.c
> +++ b/fs/compat.c
> @@ -1233,7 +1233,7 @@ static int compat_count(compat_uptr_t __user *argv, int max)
> if (!p)
> break;
> argv++;
> - if(++i > max)
> + if (i++ >= max)
> return -E2BIG;
> }
> }
> diff --git a/fs/exec.c b/fs/exec.c
> index 9bf0476..7766839 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -389,7 +389,7 @@ static int count(char __user * __user * argv, int max)
> if (!p)
> break;
> argv++;
> - if(++i > max)
> + if (i++ >= max)
> return -E2BIG;
> cond_resched();
> }
next prev parent reply other threads:[~2008-09-19 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 15:50 [PATCH] fix count(), compat_count() bounds checking Jason Baron
2008-09-19 23:06 ` Peter Zijlstra [this message]
2008-09-19 23:10 ` Ollie Wild
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=1221865573.8359.2.camel@lappy.programming.kicks-ass.net \
--to=a.p.zijlstra@chello.nl \
--cc=aaw@google.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.