Hi Greg, These are the part II 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 13 commits, - 5 commits were marked for stable but can't be applied cleanly to 3.4.x. - 1 commit has stable tag. It had been backported to 3.4.x, but with an incorrect subject and changelog.(*) - 7 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: baf48b7f96f5 setfacl removes part of ACL when setting POSIX ACLs to Samba 06335856d22e CIFS: Fix error handling in cifs_push_mandatory_locks 640c4ad6d759 ecryptfs: Fix memory leakage in keystore.c 55a058d4a89c fs: cachefiles: add support for large files in filesystem caching d08b0a5594dd perf: Fix perf ring buffer memory ordering and cherry-pick those commits from mainline: 8c4f3c3fa968 ftrace: Check module functions being traced on reload 201c373e8e48 sched/debug: Limit sd->*_idx range on sysctl fd9b86d37a60 sched/debug: Fix sd->*_idx limit range avoiding overflow c481420248c6 perf: Fix error return code 80902822658a tracing: Keep overwrite in sync between regular and snapshot buffers There are 2 other commits that need some adjustments. The following patches are the backports. (*) The commit is 51e8eac1d513 (ring-buffer: Fix NULL pointer if rb_set_head_page() fails) -- fs/cifs/cifsfs.c | 24 ++++++++++++++++++++++++ fs/cifs/cifsfs.h | 4 ++++ fs/cifs/file.c | 6 +++++- fs/stat.c | 5 +++-- 4 files changed, 36 insertions(+), 3 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