On Wed, 2008-06-08 at 14:26 +0300, Denys Fedoryshchenko wrote:I have done extensive testing with and with optind=0 and optind=1 and i didnt see any breakage with either. I have a feeling that setting optind to 0 in your case to avoid the crash maybe hiding something else - but i cant find what that something else is since i am just simulating what you are doing. If the iptables folks have changed it to reset to 0, then I dont see any harm in resetting. So ACK to both your patches. cheers, jamal PS:- dont wanna sound anal - and you dont have to do this if you dont have time; but if you put the resetting of optind and the flags in a separate patch from the freeing, that would be even better. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Andrew Morton | -mm merge plans for 2.6.23 |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Gabriel C | Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS] |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| David Miller | [GIT]: Networking |
| Thomas Jarosch | Re: TCP connection stalls under 2.6.24.7 |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
