public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: davidm@HPL.HP.COM
Cc: akpm@zip.com.au, neilb@cse.unsw.edu.au, braam@clusterfs.com,
	davem@redhat.com, Martin Schwidefsky <schwidefsky@de.ibm.com>,
	tridge@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysctl-controlled number of groups.
Date: Thu, 25 Sep 2003 18:08:25 +1000	[thread overview]
Message-ID: <20030925082720.9E6542C3B6@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 24 Sep 2003 21:19:39 MST." <16242.27867.715648.392875@napali.hpl.hp.com>

In message <16242.27867.715648.392875@napali.hpl.hp.com> you write:
> >From the ia64-side, it looks mostly fine to me.  Some minor things:
> 
>  - Typo in first sentence of patch comment (can be -> to be ?)

Thanks, fixed.

>  - If I'm reading the patch right, there will be identical sys32_getgroups16()
>    definitions in .../ia32/sys_ia32.c and and compat_linux.c; did you mean
>    to name the latter compat_getgroups16()?  (ditto for setgroups16 and s390
>    and sparc64, i think)

You're not reading it right: I didn't change the names, but since
these (your) versions call the normal ones, I added the extern decl.

>  - I suspect removing NGROUPS from param.h will break glibc and/or user-level
>    apps.  param.h is one of those kernel files that are directly exposed
>    to user-level; may want to keep NGROUPS inside an #ifndef __KERNEL__.

AFAICT, they should use NGROUPS_MAX from limits.h, which I left.

Thanks,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2003-09-25  8:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25  3:21 [PATCH] sysctl-controlled number of groups Rusty Russell
2003-09-25  4:14 ` Tim Hockin
2003-09-25  8:17   ` Rusty Russell
2003-09-25  4:19 ` David Mosberger
2003-09-25  8:08   ` Rusty Russell [this message]
2003-09-25  7:15 ` Arjan van de Ven
2003-09-25  7:25 ` William Lee Irwin III
2003-09-25  8:23   ` Rusty Russell

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=20030925082720.9E6542C3B6@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@zip.com.au \
    --cc=braam@clusterfs.com \
    --cc=davem@redhat.com \
    --cc=davidm@HPL.HP.COM \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=schwidefsky@de.ibm.com \
    --cc=tridge@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox