Re: [request for stable inclusion]: 3 patch related to oom killer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I've already sent these to stable mailing list.

On 2014/9/12 10:22, Wang Nan wrote:
> Hi Greg,
> 
> Upstream commit 0c740d0afc3bff0a097ad03a1c8df92757516f5c and
> 1da4db0cd5c8a31d4468ec906b413e75e604b465 looks ignored by 3.10 (they are
> included by 3.12.22). Without these patches we meet real deadlock in oom killer code.
> 
> They can not be clearly cherry-pick to 3.10.54 because 3.10 LTS doesn't
> contain 80628ca06c5d42929de6bc22c0a41589a834d151. So could you please quese
> following 3 patches into 3.10 stable?
> 
> 80628ca06c5d42929de6bc22c0a41589a834d151:
>   kernel/fork.c:copy_process(): unify CLONE_THREAD-or-thread_group_leader code
> 
> 0c740d0afc3bff0a097ad03a1c8df92757516f5c
>   introduce for_each_thread() to replace the buggy while_each_thread()
> 
> 1da4db0cd5c8a31d4468ec906b413e75e604b465
>   oom_kill: change oom_kill.c to use for_each_thread()
> 
> Thank you!
> 
> .
> 

--
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




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]