Skip to contentSkip to conversation

Swapping-over-nbd deadlock fixed?

DISCUSSION Jeff Garzik 3 participants 3 messages Dec 12, 2000

lore
Share & tools
lore
#0 lore raw

I see in the 2.2.18 release notes that a deadlock, related to swapping over a network via nbd, was fixed. Is this bug present in 2.4.x-test?

Signature · 7 lines
Jeff Garzik         |
Building 1024       | These are not the J's you're lookin' for.
MandrakeSoft        | It's an old Jedi mind trick.
-
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/
#1 lore raw
Quoted 2 lines · Jeff Garzik

I see in the 2.2.18 release notes that a deadlock, related to swapping over a network via nbd, was fixed. Is this bug present in 2.4.x-test?

The bug is not related to swapping via nbd.

The problem happens because the allocation code (kmalloc) which is called inside the nbd request function can end up trying to sync dirty buffers, going to back to the nbd request function.

2.4 is safe.

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

#2 lore raw
In reply to Jeff Garzik
Quoted 3 lines · Jeff Garzik

I see in the 2.2.18 release notes that a deadlock, related to swapping over a network via nbd, was fixed. Is this bug present in 2.4.x-test?

It _should_ be fixed in 2.4 as well. Then again, I don't know if there are any other deadlocks left .. ;)

regards,

Rik
--
Hollywood goes for world dumbination,

	Trailer at 11.

		http://www.surriel.com/

http://www.conectiva.com/ http://distro.conectiva.com.br/

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