From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>,
"Linux Kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Please pull bugfixes for the NFS client
Date: Thu, 21 Jun 2012 22:58:01 +0000 [thread overview]
Message-ID: <1340319479.18403.3.camel@lade.trondhjem.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1809 bytes --]
Hi Linus,
The following changes since commit 39a50b42f7026027b54131291ad0f350100eac95:
Merge branch 'hfsplus' (2012-06-17 14:40:35 -0700)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-3.5-3
for you to fetch changes up to b1027439dff844675f6c0df97a1b1d190791a699:
NFS: Force the legacy idmapper to be single threaded (2012-06-20 14:38:11 -0400)
Cheers,
Trond
----------------------------------------------------------------
NFS client bugfixes for Linux 3.5
Fixes include:
- Fix a write hang due to an uninitalised variable when !defined(CONFIG_NFS_V4)
- Address upcall races in the legacy NFSv4 idmapper
- Remove an O_DIRECT refcounting issue
- Fix a pNFS refcounting bug when the file layout metadata server is also
acting as a data server
- Fix a pNFS module loading race.
----------------------------------------------------------------
Bryan Schumaker (1):
NFS: Force the legacy idmapper to be single threaded
Trond Myklebust (4):
NFSv4.1: Fix umount when filelayout DS is also the MDS
NFSv4.1: Fix a race in set_pnfs_layoutdriver
NFS: Fix a refcounting issue in O_DIRECT
NFS: Initialise commit_info.rpc_out when !defined(CONFIG_NFS_V4)
fs/nfs/client.c | 1 -
fs/nfs/direct.c | 1 +
fs/nfs/idmap.c | 13 ++++++++-----
fs/nfs/inode.c | 2 +-
fs/nfs/pnfs.c | 13 +++++++++----
include/linux/nfs_fs_sb.h | 1 +
6 files changed, 20 insertions(+), 11 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2012-06-21 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 22:58 Myklebust, Trond [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-14 16:00 Myklebust, Trond
2011-09-15 18:50 Trond Myklebust
2011-03-28 7:04 Trond Myklebust
2010-08-18 22:44 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=1340319479.18403.3.camel@lade.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®