Re: [PATCH] [2.5] Non-blocking write can block

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Wed Jun 04 2003 - 11:47:29 EST

Next message: Linus Torvalds: "RE: [PATCH] [2.5] Non-blocking write can block"
Previous message: Shawn: "iptables & 2.5 problem"
In reply to: Linus Torvalds: "Re: [PATCH] [2.5] Non-blocking write can block"
Next in thread: Linus Torvalds: "Re: [PATCH] [2.5] Non-blocking write can block"
Reply: Linus Torvalds: "Re: [PATCH] [2.5] Non-blocking write can block"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mer, 2003-06-04 at 15:35, Linus Torvalds wrote:
> In general, we shouldn't do this, unless somebody can show an application
> where it really matters. Taking internal kernel locking into account for
> "blockingness" easily gets quite complicated, and there is seldom any real
> point to it.

Hanging shutdown is the obvious one. With 2.0/2.2 we had a similar
problem and fixed it.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Linus Torvalds: "RE: [PATCH] [2.5] Non-blocking write can block"
Previous message: Shawn: "iptables & 2.5 problem"
In reply to: Linus Torvalds: "Re: [PATCH] [2.5] Non-blocking write can block"
Next in thread: Linus Torvalds: "Re: [PATCH] [2.5] Non-blocking write can block"
Reply: Linus Torvalds: "Re: [PATCH] [2.5] Non-blocking write can block"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Jun 07 2003 - 22:00:24 EST