On Wed, 8 Feb 2006, Andrew Morton wrote: > > I think it should be put into 2.6.16. Andrew? > > Does every single caller of __alloc_pages(__GFP_FS) correctly handle a NULL > return? I doubt it, in which case this patch will cause oopses and hangs. If a caller cannot handle NULL then __GFP_NOFAIL has to be set, right? So we will never get to the piece of code under discussion. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Terminate process that fails on a constrained allocation
- From: Andrew Morton <[email protected]>
- Re: Terminate process that fails on a constrained allocation
- References:
- Terminate process that fails on a constrained allocation
- From: Christoph Lameter <[email protected]>
- Re: Terminate process that fails on a constrained allocation
- From: Andi Kleen <[email protected]>
- Re: Terminate process that fails on a constrained allocation
- From: Paul Jackson <[email protected]>
- Re: Terminate process that fails on a constrained allocation
- From: Andi Kleen <[email protected]>
- Re: Terminate process that fails on a constrained allocation
- From: Andrew Morton <[email protected]>
- Terminate process that fails on a constrained allocation
- Prev by Date: Re: Incomprehensible Boot freeze & Crash - Kernel 2.6.12
- Next by Date: Re: Terminate process that fails on a constrained allocation
- Previous by thread: Re: Terminate process that fails on a constrained allocation
- Next by thread: Re: Terminate process that fails on a constrained allocation
- Index(es):
 |