Re: [lkml]Re: VM problems still in 2.2.18

[Alan Cox]

> o     don't wait I/O completion to avoid deadlocking on the i_sem
> o     swap_out returns 1 and memory balancing code so thinks we did progress
>       in freeing memory and goes to allocate memory from the freelist
>       without waiting I/O completion
> o     repeat N times the above

so the actual problem is either - the returning 1 when it is the wrong answer
- or the failure to block somewhere else (where its safe) based on a kpiod
maintained semaphore ?

> Yes, the same `current' context must run the down/up pair of calls and as you
> said it is legal to rely on it on all the places it's used.

I assume thats not an issue to reiserfs ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/