linux-kernel - [GIT PULL] Please pull one SUNRPC client bugfix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 11 Jan 2013 18:05:28 +0000
From:	"Myklebust, Trond" <Trond.Myklebust@...app.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	linux-kernel <linux-kernel@...r.kernel.org>,
	Linux NFS mailing list <linux-nfs@...r.kernel.org>
Subject: [GIT PULL] Please pull one SUNRPC client bugfix

The following changes since commit d287b8750e47c1702dab0e37ac11012bb751ece0:

  Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2013-01-07 09:41:20 -0800)

are available in the git repository at:


  git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-3.8-3

for you to fetch changes up to 87ed50036b866db2ec2ba16b2a7aec4a2b0b7c39:

  SUNRPC: Ensure we release the socket write lock if the rpc_task exits early (2013-01-08 14:30:43 -0500)

----------------------------------------------------------------
NFS client bugfixe for Linux 3.8

- Fix a socket lock leak in net/sunrpc/xprt.c

----------------------------------------------------------------
Trond Myklebust (1):
      SUNRPC: Ensure we release the socket write lock if the rpc_task exits early

 net/sunrpc/sched.c |  3 +--
 net/sunrpc/xprt.c  | 12 ++++++++++--
 2 files changed, 11 insertions(+), 4 deletions(-)

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@...app.com
www.netapp.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/