Hi Greg, These are the part III commits that I've analized from the list of upstream commits that have been backported to 3.2 but missing from 3.4. For the 15 commits, - 13 commits were marked for stable but can't be applied cleanly to 3.4.x. - 2 commits have no stable tag. I've found out why they were backported to 3.2.x, and I'm sure they should be applied to 3.4.x. Please cherry-pick these commits from 3.2.x: a687a58fd0fa NFSv4 wait on recovery for async session errors bca06620c941 nfsd4: fix xdr decoding of large non-write compounds 70bea7f2c038 NFSv4.1: integer overflow in decode_cb_sequence_args() 7e6c247f30c6 nfsd: don't run get_file if nfs4_preprocess_stateid_op return error 1bf2642f4cb2 NFS: nfs_getaclargs.acl_len is a size_t 9ca2044f9041 NFSv4.1: Fix a race in pNFS layoutcommit 3c5add9c302a NFSv4.1: Don't decode skipped layoutgets 78e3ae2d57c0 NFSv4.1: Handle NFS4ERR_DELAY when resetting the NFSv4.1 session 4725f1715429 dm bufio: avoid a possible __vmalloc deadlock e0179c31e081 dm snapshot: add missing module aliases 4e19de3be14c md/raid10: fix "enough" function for detecting if array is failed. There are 4 other commits that need some adjustments. The following are the backports. -- drivers/md/dm-bufio.c | 26 +++++++++- drivers/md/dm-mpath.c | 18 +++++-- drivers/md/dm-snap.c | 73 +++++++++++++++++++++++++--- drivers/md/dm-thin.c | 4 +- drivers/md/persistent-data/dm-btree-remove.c | 46 +++++++++--------- drivers/md/raid10.c | 8 +-- fs/nfs/callback_xdr.c | 6 +-- fs/nfs/nfs4proc.c | 23 ++------- fs/nfs/nfs4state.c | 14 +++++- fs/nfs/pnfs.c | 19 +++++++- fs/nfsd/nfs4proc.c | 8 +-- fs/nfsd/nfs4xdr.c | 2 +- fs/nfsd/vfs.c | 5 +- 13 files changed, 183 insertions(+), 69 deletions(-) -- 1.8.2.2 -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html