:> Let me put it another way: I think this sort of thing is an excellent
:> example of introducing unnecessary kernel bloat into the system. Who
:> gives a fart whether someone can port scan you efficiently or
:> anonymously or not? I get port scanned every day. Most hackers d
:> It's not worth doing. We would be introducing unnecessary cpu burn on
:> every single packet we sent out, all to solve a problem that doesn't
:> really exist.
:
:Well, that's why it's a sysctl defaulting to off in my patch. Don't
:turn it on if you don't want to.
:
:Kris
Let
:No reasoning. You do not need the htons(). The fragment ids just
:need to be unique. An htons() does not change that property. I dont
:like that code very much. A variable-block-size cipher in counter
:mode would do the job better.
:
:However, what many ppl do not realize is that you can us
I think there is some confusion over ref counts here. I'm going
to try to be clear: You *cannot* use a 1->0 transition on a ref
count to cleanup self referential loops in socket message queues
from file descriptor passing. Because no 1->0 transition will
ever occur, even if
:Hmm, the last time i looked at this, I believe the whole thing was
:dealt with by not increasing the file descriptor reference count
:when it was put in the message header. If process A closed the
:descriptor before process B actually recvmsg()d it, it would be
:EBADF. The recvmsg() actual
:> No waste at all, Alfred, the file descriptor passing code had been
:
:Are you saying the code in place is broken? If so I'll spend some
:time looking at it and the Linux implementation to figure if at
:least one of us gets it right and try to find some sort of solution.
No, *had*, no
:I guess the gc has to stay.
:
:dammit. :)
:
:My apologies for wasting everyone's time here.
:
:--
:-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
No waste at all, Alfred, the file descriptor passing code had been
broken for over 10 years precisely because of its complexity.
:I believe that your changes have been sorely needed for many
:years. While I would like to see regular mbufs given a callback
:mechanism, your present approach of using an mbuf cluster
:solves 90% of the problem.
:
: Kirk McKusick
... Aflred, be careful that you don't break things we
