commit-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

hurd-l4/doc hurd-on-l4.tex


From: Marcus Brinkmann
Subject: hurd-l4/doc hurd-on-l4.tex
Date: Wed, 03 Sep 2003 14:19:15 -0400

CVSROOT:        /cvsroot/hurd
Module name:    hurd-l4
Branch:         
Changes by:     Marcus Brinkmann <address@hidden>       03/09/03 14:19:15

Modified files:
        doc            : hurd-on-l4.tex 

Log message:
        Add info about DoS attack when accepting messages.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/hurd/hurd-l4/doc/hurd-on-l4.tex.diff?tr1=1.16&tr2=1.17&r1=text&r2=text

Patches:
Index: hurd-l4/doc/hurd-on-l4.tex
diff -u hurd-l4/doc/hurd-on-l4.tex:1.16 hurd-l4/doc/hurd-on-l4.tex:1.17
--- hurd-l4/doc/hurd-on-l4.tex:1.16     Sun Aug 31 16:07:36 2003
+++ hurd-l4/doc/hurd-on-l4.tex  Wed Sep  3 14:19:15 2003
@@ -1392,6 +1392,19 @@
 such places need to be rewritten in a different way (for example using
 extra threads).
 
+\begin{comment}
+  What happens if a client does not go into the receive phase after a
+  send, but instead does another send, and another one, quickly many
+  sends, as fast as possible?  A carelessly written server might
+  create worker threads for each request.  Instead, the server should
+  probably reject to accept a request from a client thread that
+  already has a pending request, so the number of worker threads is
+  limited to the number of client threads.
+  
+  This also makes interrupting an RPC operation easier (the client
+  thread ID can be used to identify the request to interrupt).
+\end{comment}
+
 
 \subsection{Notifications}
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]