All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jerome Marchand <jmarchan@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix integer overflow in groups_search
Date: Fri, 3 Sep 2010 16:54:46 -0700	[thread overview]
Message-ID: <20100903165446.378e8ceb.akpm@linux-foundation.org> (raw)
In-Reply-To: <4C7FC0B4.3040005@redhat.com>

On Thu, 02 Sep 2010 17:20:20 +0200
Jerome Marchand <jmarchan@redhat.com> wrote:

> 
> gid_t is a unsigned int. If group_info contains a gid greater than
> MAX_INT, groups_search() function may look on the wrong side of the 
> search tree.
> This solves some unfair "permission denied" problems.
> 
> Signed-off-by: Jerome Marchand <jmarchan@redhat.com>
> ---
> diff --git a/kernel/groups.c b/kernel/groups.c
> index 53b1916..253dc0f 100644
> --- a/kernel/groups.c
> +++ b/kernel/groups.c
> @@ -143,10 +143,9 @@ int groups_search(const struct group_info *group_info, gid_t grp)
>  	right = group_info->ngroups;
>  	while (left < right) {
>  		unsigned int mid = (left+right)/2;
> -		int cmp = grp - GROUP_AT(group_info, mid);
> -		if (cmp > 0)
> +		if (grp > GROUP_AT(group_info, mid))
>  			left = mid + 1;
> -		else if (cmp < 0)
> +		else if (grp < GROUP_AT(group_info, mid))
>  			right = mid;
>  		else
>  			return 1;

hah, that's some pretty ancient code there.  You must have a lot of
groups.

The patch is a no-brainer and I guess you've encountered the bug in
real kernels so I think we'll wave the fix at the -stable guys for
backporting, OK?


      reply	other threads:[~2010-09-03 23:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 15:20 [PATCH] fix integer overflow in groups_search Jerome Marchand
2010-09-03 23:54 ` Andrew Morton [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=20100903165446.378e8ceb.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jmarchan@redhat.com \
    --cc=linux-kernel@vger.kernel.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.