LKML Archive on
help / color / mirror / Atom feed
From: Trond Myklebust <>
To: Linus Torvalds <>
Subject: [GIT] Please pull NFS client bugfixes
Date: Thu, 19 Nov 2009 11:35:08 -0500	[thread overview]
Message-ID: <1258648508.30333.16.camel@localhost> (raw)

Hi Linus,

Please pull from the "bugfixes" branch of the repository at

   git pull git:// bugfixes

This will update the following files through the appended changesets.


 fs/nfs/nfs4proc.c |    2 +-
 net/sunrpc/addr.c |   18 ++++++++----------
 2 files changed, 9 insertions(+), 11 deletions(-)

commit 1e360a60b24ad8f8685af66fa6de10ce46693a4b
Author: Chuck Lever <>
Date:   Fri Nov 13 10:52:55 2009 -0500

    SUNRPC: Address buffer overrun in rpc_uaddr2sockaddr()
    The size of buf[] must account for the string termination needed for
    the first strict_strtoul() call.  Introduced in commit a02d6926.
    Fábio Olivé Leite points out that strict_strtoul() requires _either_
    '\n\0' _or_ '\0' termination, so use the simpler '\0' here instead.
    See .
    Signed-off-by: Chuck Lever <>
    Signed-off-by: Fábio Olivé Leite <>
    Signed-off-by: Trond Myklebust <>

commit 96d25e532234bec1a1989e6e1baf702d43a78b0d
Author: Trond Myklebust <>
Date:   Wed Nov 11 16:15:42 2009 +0900

    NFSv4: Fix a cache validation bug which causes getcwd() to return ENOENT
    Changeset a65318bf3afc93ce49227e849d213799b072c5fd (NFSv4: Simplify some
    cache consistency post-op GETATTRs) incorrectly changed the getattr
    bitmap for readdir().
    This causes the readdir() function to fail to return a
    fileid/inode number, which again exposed a bug in the NFS readdir code that
    causes spurious ENOENT errors to appear in applications (see
    The immediate band aid is to revert the incorrect bitmap change, but more
    long term, we should change the NFS readdir code to cope with the
    fact that NFSv4 servers are not required to support fileids/inode numbers.
    Reported-by: Daniel J Blueman <>
    Signed-off-by: Trond Myklebust <>

             reply	other threads:[~2009-11-19 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19 16:35 Trond Myklebust [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-27 21:35 Trond Myklebust
2008-10-28 19:26 [GIT] Please pull nfs " Trond Myklebust

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1258648508.30333.16.camel@localhost \ \ \ \ \
    --subject='Re: [GIT] Please pull NFS client bugfixes' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).