linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Rees <rees@umich.edu>
To: "Finney, Sean" <Sean.Finney@sonyericsson.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"bfields@fieldses.org" <bfields@fieldses.org>
Subject: Re: [PATCH v2 1/2] nfs-utils: mountd: Use a dynamic buffer for storing lists of gid's
Date: Thu, 7 Apr 2011 11:01:20 -0400	[thread overview]
Message-ID: <20110407150120.GA12596@merit.edu> (raw)
In-Reply-To: <A50602A820F61543B29992A418BB321B66E18F8A5E@seldmbx01.corpusers.net>

Finney, Sean wrote:

  > I would re-word this.  The list isn't static, the list pointer is.  I don't
  > think you need to mention that, it's just confusing.  "Use malloc/realloc to
  > grow the list on an as-needed basis."
  
  Okay.  I was trying to just put a hint that there was a persistant
  buffer that would hang around through multiple invocations, though
  perhaps that's a little too much 'implementation details'.  Totally fine
  with modifying the description either way :)

If it were me, I would alloc and free the list each time rather than keeping
it around.  It's not like malloc is super expensive.  But that's a matter of
taste.

  > BUGS
  >        In  glibc  versions  before  2.3.3, the implementation of this function
  >        contains a buffer-overrun bug: it returns the complete list  of  groups
  >        for  user  in  the array groups, even when the number of groups exceeds
  >        *ngroups.
  
  Yuck.  The function is also not in POSIX or any other standards, so
  maybe it's worth discussing at a later point whether getgroups(2) would
  be a better interface to use, even if it means an extra step or two.

There's no sense in making nfs-utils portable to non-linux, so depending on
glibc is probably ok.  2.3.3 was released in December 2003 so I would argue
we don't care about the buffer-overrun bug.

  Anyway, I will re-spin this patch with the two changes that you've
  suggested and submit it tomorrow.   Care to take a look at patch
  2/2?  :)

It looked fine to me.

      parent reply	other threads:[~2011-04-07 15:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  8:02 Fixes for NFS in environments with large group memberships Finney, Sean
     [not found] ` <A50602A820F61543B29992A418BB321B66E18F8A4A-g6SuDuYnGwoBLpZRX7oUTsm4BeyDBExM@public.gmane.org>
2011-04-05 23:35   ` J. Bruce Fields
2011-04-07  5:53     ` Finney, Sean
2011-04-07  7:22     ` [PATCH v2 1/2] nfs-utils: mountd: Use a dynamic buffer for storing lists of gid's Sean Finney
2011-04-07  7:22       ` [PATCH v2 2/2] nfs-utils: Increase the stdio file buffer size for procfs files Sean Finney
2011-04-07 12:22       ` [PATCH v2 1/2] nfs-utils: mountd: Use a dynamic buffer for storing lists of gid's Jim Rees
2011-04-07 14:15         ` Finney, Sean
2011-04-07 14:29           ` Chuck Lever
2011-04-07 15:01           ` Jim Rees [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=20110407150120.GA12596@merit.edu \
    --to=rees@umich.edu \
    --cc=Sean.Finney@sonyericsson.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@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 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).