On Tue, Feb 18, 2014 at 03:37:09PM +0800, Li Zefan wrote:
> Hi Greg,
>
> We've started to analize the list of upstream commits that have been
> backported to 3.2 but missing from 3.4.
>
> For the 18 commits that I've analized,
> - 4 commits have been backported to 3.4. My script failed to detect them.
> - 1 commit is obviosly not a bug fix, don't know why it went into 3.2.x. (*)
> - 7 commits were marked for stable but can't be applied cleanly to 3.4.
> - 5 commits have no stable tag. I've found out why they were backported to
> 3.2.x,
> and I'm sure they shoud be applied to 3.4.x.
> - 1 commit were 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. (**)
>
> So 13 out of 18 commits should be backported.
>
> Please cherry-pick those commits from 3.2.x:
>
> 2492cd118dc5 target/file: Use O_DSYNC by default for FILEIO backends
> 14b557c19dbe target/file: Re-enable optional fd_buffered_io=1 operation
> 0f3cbc35d209 KVM: Fix buffer overflow in kvm_set_irq()
> 6ed6791a1697 PM / Hibernate: Hibernate/thaw fixes/improvements
> 2028a493b8ff Input: synaptics - handle out of bounds values from the hardware
> e551857183b5 virtio-blk: Use block layer provided spinlock
> 1b772a147a18 lib/vsprintf.c: kptr_restrict: fix pK-error in SysRq
> show-all-timers(Q) (**)
Ah, there's the (**) footnote :)
> c52f6cc5d3e4 ("nfs: tear down caches in nfs_init_writepagecache when
> allocation fails")
>
> cherry-pick those commits from mainline:
>
> 556061b00c9f sched/nohz: Fix rq->cpu_load[] calculations
> 5aaa0b7a2ed5 sched/nohz: Fix rq->cpu_load calculations some more
>
> There're 3 other commits that need trivial context adjustments. I'll send out
> the backports.
>
> (*) The commit is 0c68ab1b2387 (USB: cdc-wdm: add debug messages on cleanup)
Thanks so much for doing this, I should have it all now queued up
properly, please let me know if I've missed anything.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
