Hi Greg, These are the part 2 commits that I've analyzed from the list of upstream commits that have been backported to 3.2 but missing from 3.4. For the 9 commits, - 6 commits were marked for stable but can't be applied cleanly to 3.4. - 1 commit was marked for stable and can be applied cleanly and the fix is obviously correct, don't know why it's absent from 3.4.x. (*) - 1 commit has no stable tag. I've found out why it was backported to 3.2.x, and I'm sure it should be applied to 3.4.x. (**) - 1 commit has been reverted in upstream and 3.2.x. Please cherry-pick those commits from 3.2.x: e06c33874253 Staging: zram: Fix memory leak by refcount mismatch dccfb68c2630 Staging: zram: Fix access of NULL pointer 498a727b33ee zram: allow request end to coincide with disksize e1c3e37d2c1d zram: protect sysfs handler from invalid memory access 624d1705fa1d zram: avoid access beyond the zram device 29c303b89a1b zram: destroy all devices on error recovery path in zram_init() fd162a76f160 zram: avoid invalid memory access in zram_exit() 41247561dc21 zram: Fix deadlock bug in partial read/write (*) The commit is 624d1705fa1d (zram: avoid access beyond the zram device) (**) The commit is 498a727b33ee (zram: allow request end to coincide with disksize) --- drivers/staging/zram/zram_drv.c | 38 ++++++++++++++++++++++++------------ drivers/staging/zram/zram_sysfs.c | 27 +++++++++++++++++++------ 2 files changed, 45 insertions(+), 20 deletions(-) -- 1.7.7 -- 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