Re: [patch] oom: avoid killing kthreads if they assume the oom killed thread's mm

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

 



On Tue 26-07-11 15:05:23, David Rientjes wrote:
> On Tue, 26 Jul 2011, Michal Hocko wrote:
> 
> > > After selecting a task to kill, the oom killer iterates all processes and
> > > kills all other threads that share the same mm_struct in different thread
> > > groups.  It would not otherwise be helpful to kill a thread if its memory
> > > would not be subsequently freed.
> > > 
> > > A kernel thread, however, may assume a user thread's mm by using
> > > use_mm().  This is only temporary and should not result in sending a
> > > SIGKILL to that kthread.
> > 
> > Good catch. Have you ever seen this happening?
> > 
> 
> No, this is just another patch to make the kernel more use_mm()-friendly.  
> Before that capability was introduced, it was possible to assume that a 
> kthread would always have a NULL mm pointer, so it wasn't previously 
> required for this code.

OK

Thanks
-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]