From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mailing List Linux NFS <linux-nfs@vger.kernel.org>,
Linux linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client fixes
Date: Wed, 10 Apr 2013 15:59:28 +0000 [thread overview]
Message-ID: <1365609573.8465.5.camel@leira.trondhjem.org> (raw)
Hi Linus,
The following changes since commit 1166fde6a923c30f4351515b6a9a1efc513e7d00:
SUNRPC: Add barriers to ensure read ordering in rpc_wake_up_task_queue_locked (2013-03-25 11:23:40 -0400)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-3.9-4
for you to fetch changes up to fa332941c0c7c00e3420078268b7558d0ef792b5:
NFSv4: Fix another potential state manager deadlock (2013-04-09 13:19:35 -0400)
----------------------------------------------------------------
NFS client bugfixes for Linux 3.9
- Stable fix for memory corruption issues in nfs4[01]_walk_client_list
- Stable fix for an Oopsable bug in rpc_clone_client
- Another state manager deadlock in the NFSv4 open code
- Memory leaks in nfs4_discover_server_trunking and rpc_new_client
----------------------------------------------------------------
Chuck Lever (1):
SUNRPC: Remove extra xprt_put()
Trond Myklebust (4):
NFSv4: Fix a memory leak in nfs4_discover_server_trunking
NFSv4/4.1: Fix bugs in nfs4[01]_walk_client_list
SUNRPC: Fix a potential memory leak in rpc_new_client
NFSv4: Fix another potential state manager deadlock
fs/nfs/nfs4client.c | 44 ++++++++++++++++++++++++++++----------------
fs/nfs/nfs4proc.c | 1 +
fs/nfs/nfs4state.c | 8 +++++++-
net/sunrpc/clnt.c | 11 +++--------
4 files changed, 39 insertions(+), 25 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next reply other threads:[~2013-04-10 15:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 15:59 Myklebust, Trond [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-26 20:12 Trond Myklebust
2019-03-26 22:25 ` pr-tracker-bot
2017-10-24 22:56 Trond Myklebust
2016-09-12 19:28 Trond Myklebust
2016-02-23 18:33 Trond Myklebust
2014-09-12 17:04 Trond Myklebust
2014-08-29 19:35 Trond Myklebust
2014-08-25 14:55 Trond Myklebust
2014-02-19 14:13 Trond Myklebust
2014-02-19 14:40 ` Trond Myklebust
2014-02-04 16:52 Trond Myklebust
2013-07-19 19:27 Myklebust, Trond
2013-01-31 19:47 Myklebust, Trond
2012-08-22 15:41 Myklebust, Trond
2011-06-21 18:36 Trond Myklebust
2010-12-10 18:05 Trond Myklebust
2010-12-09 3:11 Trond Myklebust
2010-04-13 21:54 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=1365609573.8465.5.camel@leira.trondhjem.org \
--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
all inboxes | Powered by JetHome®