| commit | 82e6bfe2fbc4d48852114c4f979137cd5bf1d1a8 | [log] [tgz] |
|---|---|---|
| author | Jan Engelhardt <jengelh@inai.de> | Fri Sep 21 22:26:52 2012 +0000 |
| committer | Pablo Neira Ayuso <pablo@netfilter.org> | Wed Sep 26 01:33:16 2012 +0200 |
| tree | 97fd3c06795902c807a381c0bef3bc2e9bfd2966 | |
| parent | 3e10986d1d698140747fcfc2761ec9cb64c1d582 [diff] |
netfilter: xt_limit: have r->cost != 0 case work Commit v2.6.19-rc1~1272^2~41 tells us that r->cost != 0 can happen when a running state is saved to userspace and then reinstated from there. Make sure that private xt_limit area is initialized with correct values. Otherwise, random matchings due to use of uninitialized memory. Signed-off-by: Jan Engelhardt <jengelh@inai.de> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>