<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/net/netfilter, branch v3.8</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v3.8</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v3.8'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2013-02-06T00:56:50Z</updated>
<entry>
<title>ipvs: sctp: fix checksumming on snat and dnat handlers</title>
<updated>2013-02-06T00:56:50Z</updated>
<author>
<name>Daniel Borkmann</name>
<email>dborkman@redhat.com</email>
</author>
<published>2013-02-05T16:21:31Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=4b47bc9a9e69141ed3a854c57601f548e82c78ba'/>
<id>urn:sha1:4b47bc9a9e69141ed3a854c57601f548e82c78ba</id>
<content type='text'>
In our test lab, we have a simple SCTP client connecting to a SCTP
server via an IPVS load balancer. On some machines, load balancing
works, but on others the initial handshake just fails, thus no
SCTP connection whatsoever can be established!

We observed that the SCTP INIT-ACK handshake reply from the IPVS
machine to the client had a correct IP checksum, but corrupt SCTP
checksum when forwarded, thus on the client-side the packet was
dropped and an intial handshake retriggered until all attempts
run into the void.

To fix this issue, this patch i) adds a missing CHECKSUM_UNNECESSARY
after the full checksum (re-)calculation (as done in IPVS TCP and UDP
code as well), ii) calculates the checksum in little-endian format
(as fixed with the SCTP code in commit 4458f04c: sctp: Clean up sctp
checksumming code) and iii) refactors duplicate checksum code into a
common function. Tested by myself.

Signed-off-by: Daniel Borkmann &lt;dborkman@redhat.com&gt;
Acked-by: Julian Anastasov &lt;ja@ssi.bg&gt;
Signed-off-by: Simon Horman &lt;horms@verge.net.au&gt;
</content>
</entry>
<entry>
<title>ipvs: freeing uninitialized pointer on error</title>
<updated>2013-01-28T01:14:37Z</updated>
<author>
<name>Dan Carpenter</name>
<email>dan.carpenter@oracle.com</email>
</author>
<published>2013-01-25T15:44:57Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=b425df4cdd953a400d814b4474c9d3ec04481858'/>
<id>urn:sha1:b425df4cdd953a400d814b4474c9d3ec04481858</id>
<content type='text'>
If state != IP_VS_STATE_BACKUP then tinfo-&gt;buf is uninitialized.  If
kthread_run() fails then it means we free random memory resulting in an
oops.

Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Acked-by: Julian Anastasov &lt;ja@ssi.bg&gt;
Signed-off-by: Simon Horman &lt;horms@verge.net.au&gt;
</content>
</entry>
<entry>
<title>netfilter: x_tables: print correct hook names for ARP</title>
<updated>2013-01-13T11:54:12Z</updated>
<author>
<name>Jan Engelhardt</name>
<email>jengelh@inai.de</email>
</author>
<published>2013-01-10T12:30:05Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=5b76c4948fe6977bead2359c2054f3e6a2dcf3d0'/>
<id>urn:sha1:5b76c4948fe6977bead2359c2054f3e6a2dcf3d0</id>
<content type='text'>
arptables 0.0.4 (released on 10th Jan 2013) supports calling the
CLASSIFY target, but on adding a rule to the wrong chain, the
diagnostic is as follows:

	# arptables -A INPUT -j CLASSIFY --set-class 0:0
	arptables: Invalid argument
	# dmesg | tail -n1
	x_tables: arp_tables: CLASSIFY target: used from hooks
	PREROUTING, but only usable from INPUT/FORWARD

This is incorrect, since xt_CLASSIFY.c does specify
(1 &lt;&lt; NF_ARP_OUT) | (1 &lt;&lt; NF_ARP_FORWARD).

This patch corrects the x_tables diagnostic message to print the
proper hook names for the NFPROTO_ARP case.

Affects all kernels down to and including v2.6.31.

Signed-off-by: Jan Engelhardt &lt;jengelh@inai.de&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
</content>
</entry>
<entry>
<title>netfilter: nf_conntrack: fix BUG_ON while removing nf_conntrack with netns</title>
<updated>2013-01-12T13:12:36Z</updated>
<author>
<name>Pablo Neira Ayuso</name>
<email>pablo@netfilter.org</email>
</author>
<published>2013-01-10T15:12:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1e47ee8367babe6a5e8adf44a714c7086657b87e'/>
<id>urn:sha1:1e47ee8367babe6a5e8adf44a714c7086657b87e</id>
<content type='text'>
canqun zhang reported that we're hitting BUG_ON in the
nf_conntrack_destroy path when calling kfree_skb while
rmmod'ing the nf_conntrack module.

Currently, the nf_ct_destroy hook is being set to NULL in the
destroy path of conntrack.init_net. However, this is a problem
since init_net may be destroyed before any other existing netns
(we cannot assume any specific ordering while releasing existing
netns according to what I read in recent emails).

Thanks to Gao feng for initial patch to address this issue.

Reported-by: canqun zhang &lt;canqunzhang@gmail.com&gt;
Acked-by: Gao feng &lt;gaofeng@cn.fujitsu.com&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
</content>
</entry>
<entry>
<title>netfilter: xt_CT: fix unset return value if conntrack zone are disabled</title>
<updated>2013-01-10T12:11:00Z</updated>
<author>
<name>Pablo Neira Ayuso</name>
<email>pablo@netfilter.org</email>
</author>
<published>2013-01-10T11:42:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=4610476d89d53714ca94aae081fa035908bc137a'/>
<id>urn:sha1:4610476d89d53714ca94aae081fa035908bc137a</id>
<content type='text'>
net/netfilter/xt_CT.c: In function ‘xt_ct_tg_check_v1’:
net/netfilter/xt_CT.c:250:6: warning: ‘ret’ may be used uninitialized in this function [-Wmaybe-uninitialized]
net/netfilter/xt_CT.c: In function ‘xt_ct_tg_check_v0’:
net/netfilter/xt_CT.c:112:6: warning: ‘ret’ may be used uninitialized in this function [-Wmaybe-uninitialized]

Reported-by: Borislav Petkov &lt;bp@alien8.de&gt;
Acked-by: Borislav Petkov &lt;bp@alien8.de&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
</content>
</entry>
<entry>
<title>netfilter: xt_recent: avoid high order page allocations</title>
<updated>2013-01-04T19:14:42Z</updated>
<author>
<name>Eric Dumazet</name>
<email>edumazet@google.com</email>
</author>
<published>2013-01-03T22:18:39Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=2727de76041b2064c0b74f00a2a89678fb3efafc'/>
<id>urn:sha1:2727de76041b2064c0b74f00a2a89678fb3efafc</id>
<content type='text'>
xt_recent can try high order page allocations and this can fail.

iptables: page allocation failure: order:9, mode:0xc0d0

It also wastes about half the allocated space because of kmalloc()
power-of-two roundups and struct recent_table layout.

Use vmalloc() instead to save space and be less prone to allocation
errors when memory is fragmented.

Reported-by: Miroslav Kratochvil &lt;exa.exa@gmail.com&gt;
Reported-by: Dave Jones &lt;davej@redhat.com&gt;
Reported-by: Harald Reindl &lt;h.reindl@thelounge.net&gt;
Signed-off-by: Eric Dumazet &lt;edumazet@google.com&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
</content>
</entry>
<entry>
<title>netfilter: fix missing dependencies for the NOTRACK target</title>
<updated>2013-01-04T19:14:38Z</updated>
<author>
<name>Pablo Neira Ayuso</name>
<email>pablo@netfilter.org</email>
</author>
<published>2013-01-02T16:30:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=757ae316fb35811cfd8c67de0e0b8680ec4c1f37'/>
<id>urn:sha1:757ae316fb35811cfd8c67de0e0b8680ec4c1f37</id>
<content type='text'>
warning: (NETFILTER_XT_TARGET_NOTRACK) selects NETFILTER_XT_TARGET_CT which has unmet direct
+dependencies (NET &amp;&amp; INET &amp;&amp; NETFILTER &amp;&amp; NETFILTER_XTABLES &amp;&amp; NF_CONNTRACK &amp;&amp; (IP_NF_RAW ||
+IP6_NF_RAW) &amp;&amp; NETFILTER_ADVANCED)

Reported-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;
Reported-by: kbuild test robot &lt;fengguang.wu@intel.com&gt;
Acked-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
</content>
</entry>
<entry>
<title>netfilter: ctnetlink: fix leak in error path of ctnetlink_create_expect</title>
<updated>2012-12-26T22:02:09Z</updated>
<author>
<name>Jesper Juhl</name>
<email>jj@chaosbits.net</email>
</author>
<published>2012-12-26T11:49:40Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1310b955c804975651dca6c674ebfd1cb2b4c7ff'/>
<id>urn:sha1:1310b955c804975651dca6c674ebfd1cb2b4c7ff</id>
<content type='text'>
This patch fixes a leak in one of the error paths of
ctnetlink_create_expect if no helper and no timeout is specified.

Signed-off-by: Jesper Juhl &lt;jj@chaosbits.net&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
</content>
</entry>
<entry>
<title>netfilter: xt_hashlimit: fix namespace destroy path</title>
<updated>2012-12-26T17:14:48Z</updated>
<author>
<name>Vitaly E. Lavrov</name>
<email>lve@guap.ru</email>
</author>
<published>2012-12-24T13:42:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=32263dd1b43378b4f7d7796ed713f77e95f27e8a'/>
<id>urn:sha1:32263dd1b43378b4f7d7796ed713f77e95f27e8a</id>
<content type='text'>
recent_net_exit() is called before recent_mt_destroy() in the
destroy path of network namespaces. Make sure there are no entries
in the parent proc entry xt_recent before removing it.

Signed-off-by: Vitaly E. Lavrov &lt;lve@guap.ru&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
</content>
</entry>
<entry>
<title>netfilter: xt_recent: fix namespace destroy path</title>
<updated>2012-12-26T17:14:48Z</updated>
<author>
<name>Vitaly E. Lavrov</name>
<email>lve@guap.ru</email>
</author>
<published>2012-12-24T12:55:20Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=665e205c16c1f902ac6763b8ce8a0a3a1dcefe59'/>
<id>urn:sha1:665e205c16c1f902ac6763b8ce8a0a3a1dcefe59</id>
<content type='text'>
recent_net_exit() is called before recent_mt_destroy() in the
destroy path of network namespaces. Make sure there are no entries
in the parent proc entry xt_recent before removing it.

Signed-off-by: Vitaly E. Lavrov &lt;lve@guap.ru&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
</content>
</entry>
</feed>
