linux-kernel - nfsd fixes for 2.6.30

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>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 May 2009 15:29:12 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: nfsd fixes for 2.6.30

The following nfsd fixes are available from the for-2.6.30 branch at:

	git://linux-nfs.org/~bfields/linux.git for-2.6.30

(Note: I wasn't sure of the last one, "nfsd: silence lockdep warning":
on the one hand, it's just a warning.  On the other hand, a lot of users
may assume it's something more serious and freak out, just because
there's a backtrace in it.  Should this have been saved for the next
merge window?)

--b.

Andy Adamson (1):
      nfsd41: slots are freed with session

J. Bruce Fields (3):
      nfsd4: check for negative dentry before use in nfsv4 readdir
      lockd: fix list corruption on lockd restart
      nfsd: silence lockdep warning

Steve Wise (2):
      svcrdma: Fix dma map direction for rdma read targets
      svcrdma: clean up error paths.

 fs/lockd/svc.c                           |   15 +++++++++++----
 fs/nfsd/nfs4recover.c                    |    4 ++--
 fs/nfsd/nfs4state.c                      |    1 -
 fs/nfsd/nfs4xdr.c                        |   16 +++++++++++++++-
 net/sunrpc/xprtrdma/svc_rdma_recvfrom.c  |    2 +-
 net/sunrpc/xprtrdma/svc_rdma_sendto.c    |    3 +++
 net/sunrpc/xprtrdma/svc_rdma_transport.c |    3 ++-
 7 files changed, 34 insertions(+), 10 deletions(-)
--
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/