On Tue, 19 Dec 2000, Andrea Arcangeli wrote:
> On Mon, Dec 18, 2000 at 10:57:44PM +0100, Mikulas Patocka wrote:
> > You have small posibility that interrupt will eat up memory - interrupt in
> > process that has PF_MEMALLOC. Patch:
>
> this is not the point of getblk, to fix the getblk deadlock the only way is to
> implement a fail path in each caller and allow getblk to return NULL (as every
> other memory allocation function can do).
Failing getblk would likely introduce filesystem corruption. Look at
getblk in 2.0 - when allocating new page fails it tries to reuse existing
clean buffers or wakes up bdflush and waits until it writes them. This is
the right thing to do.
Mikulas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 23 2000 - 21:00:24 EST