linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: trond.myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] 2.6.38 bug fixes
Date: Thu, 20 Jan 2011 22:04:55 -0500	[thread overview]
Message-ID: <20110121030314.1056.96774.stgit@matisse.1015granger.net> (raw)

Hey-

Here are four patches that address recent issues discovered in 2.6.38.
They should be ready for inclusion upstream.  I say that because that
guarantees you will find bugs in them.

---

Chuck Lever (4):
      NFS: Prevent memory allocation failure in nfsacl_encode()
      NFS: nfsacl_{encode,decode} should return signed integer
      NFS: Fix "kernel BUG at fs/nfs/nfs3xdr.c:1338!"
      NFS: Fix "kernel BUG at fs/aio.c:554!"


 fs/nfs/direct.c           |   30 +++++++++++++------------
 fs/nfs/nfs3acl.c          |    4 ++-
 fs/nfs/nfs3xdr.c          |    5 +++-
 fs/nfs_common/nfsacl.c    |   54 ++++++++++++++++++++++++++++++++++-----------
 fs/posix_acl.c            |   17 +++++++++++---
 include/linux/nfsacl.h    |    4 ++-
 include/linux/posix_acl.h |    1 +
 7 files changed, 79 insertions(+), 36 deletions(-)

-- 
Chuck Lever

             reply	other threads:[~2011-01-21  3:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  3:04 Chuck Lever [this message]
2011-01-21  3:05 ` [PATCH 1/4] NFS: Fix "kernel BUG at fs/aio.c:554!" Chuck Lever
2011-01-21  3:14   ` Wengang Wang
2011-01-21  3:05 ` [PATCH 2/4] NFS: Fix "kernel BUG at fs/nfs/nfs3xdr.c:1338!" Chuck Lever
2011-01-21  3:05 ` [PATCH 3/4] NFS: nfsacl_{encode,decode} should return signed integer Chuck Lever
2011-01-21  3:05 ` [PATCH 4/4] NFS: Prevent memory allocation failure in nfsacl_encode() Chuck Lever

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=20110121030314.1056.96774.stgit@matisse.1015granger.net \
    --to=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@netapp.com \
    /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).