public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
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://git.linux-nfs.org/projects/trondmy/nfs-2.6.git bugfix=
es

This will update the following files through the appended changesets.

  Cheers,
    Trond

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

commit 1e360a60b24ad8f8685af66fa6de10ce46693a4b
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Fri Nov 13 10:52:55 2009 -0500

    SUNRPC: Address buffer overrun in rpc_uaddr2sockaddr()
   =20
    The size of buf[] must account for the string termination needed fo=
r
    the first strict_strtoul() call.  Introduced in commit a02d6926.
   =20
    F=C3=A1bio Oliv=C3=A9 Leite points out that strict_strtoul() requir=
es _either_
    '\n\0' _or_ '\0' termination, so use the simpler '\0' here instead.
   =20
    See http://bugzilla.kernel.org/show_bug.cgi?id=3D14546 .
   =20
    Reported-by: argp-YZAGAMbGdGKGw+nKnLezzg@public.gmane.org
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Signed-off-by: F=C3=A1bio Oliv=C3=A9 Leite <fleite@redhat.com>
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

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

    NFSv4: Fix a cache validation bug which causes getcwd() to return E=
NOENT
   =20
    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 c=
ode that
    causes spurious ENOENT errors to appear in applications (see
    http://bugzilla.kernel.org/show_bug.cgi?id=3D14541).
   =20
    The immediate band aid is to revert the incorrect bitmap change, bu=
t 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 n=
umbers.
   =20
    Reported-by: Daniel J Blueman <daniel.blueman@gmail.com>
    Cc: stable@kernel.org
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>



             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 [GIT] Please pull NFS client bugfixes 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:
  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=1258648508.30333.16.camel@localhost \
    --to=trond.myklebust@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox