lkml.org 
[lkml]   [1999]   [Mar]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Real fix] Re: Kernel panic: can't push onto full stack
On Tue, 2 Mar 1999, Alexander Viro wrote:

>Darn. Screw #4 - it doesn't solve anything. Add #5: block on close()
>(maybe make it an setsockopt()-controllable). BTW, from my reading of

The attakker can run setsockopt ;).

Blocking on close looks messy to me. Application suppose that close()
doesn't block indefinetely. If we want to sleep in a usually-not-sleeping
path better to sleep in connect() ;).

Andrea Arcangeli


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

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.058 / U:0.752 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site