> * Ted Unangst [2008-06-20 20:50]:
sloppy state handling use, follow these two rules:
rule one:
if you exactly understand how to use sloppy state safely, use it
NO: otherwise, don't even dream of using it, unless you come from
an linux ipfilter world, in which case, it is probably as good
as that
it is that simple. really.
the second basic rule is:
if the regular 'strict' state handling does not work for you in
specific situations, you probably already already know the
problem in enough detail and can use sloppy, for very specific
situations which you understand in excruciating detail. if you
don't understand those situations exactly go back to NO.
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Benjamin Herrenschmidt | Re: [PATCH] Remove process freezer from suspend to RAM pathway |
| Greg KH | [patch 00/73] 2.6.23-stable review |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
git: | |
| Arjan van de Ven | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
