<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/net, branch v2.6.13.2</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/net?h=v2.6.13.2</id>
<link rel='self' href='https://git.amat.us/linux/atom/net?h=v2.6.13.2'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2005-09-17T01:01:57Z</updated>
<entry>
<title>[PATCH] Fix DHCP + MASQUERADE problem</title>
<updated>2005-09-17T01:01:57Z</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2005-09-13T07:37:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=504b891bc7cc7fb76e3000b5fe91ca491eb773c5'/>
<id>urn:sha1:504b891bc7cc7fb76e3000b5fe91ca491eb773c5</id>
<content type='text'>
In 2.6.13-rcX the MASQUERADE target was changed not to exclude local
packets for better source address consistency. This breaks DHCP clients
using UDP sockets when the DHCP requests are caught by a MASQUERADE rule
because the MASQUERADE target drops packets when no address is configured
on the outgoing interface. This patch makes it ignore packets with a
source address of 0.

Thanks to Rusty for this suggestion.

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] raw_sendmsg DoS (CAN-2005-2492)</title>
<updated>2005-09-10T02:42:53Z</updated>
<author>
<name>Al Viro</name>
<email>aviro@redhat.com</email>
</author>
<published>2005-08-31T09:55:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0721a681c617fdd498f2f0f40e69895354baf099'/>
<id>urn:sha1:0721a681c617fdd498f2f0f40e69895354baf099</id>
<content type='text'>
Fix unchecked __get_user that could be tricked into generating a
memory read on an arbitrary address.  The result of the read is not
returned directly but you may be able to divine some information about
it, or use the read to cause a crash on some architectures by reading
hardware state.  CAN-2005-2492.

Fix from Al Viro, ack from Dave Miller.

Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] 32bit sendmsg() flaw (CAN-2005-2490)</title>
<updated>2005-09-10T02:42:53Z</updated>
<author>
<name>David Woodhouse</name>
<email>dwmw2@infradead.org</email>
</author>
<published>2005-09-06T08:30:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c255cda2af84db91d19944c092baf5a61c633181'/>
<id>urn:sha1:c255cda2af84db91d19944c092baf5a61c633181</id>
<content type='text'>
When we copy 32bit -&gt;msg_control contents to kernel, we walk the same
userland data twice without sanity checks on the second pass.

Second version of this patch: the original broke with 64-bit arches
running 32-bit-compat-mode executables doing sendmsg() syscalls with
unaligned CMSG data areas

Another thing is that we use kmalloc() to allocate and sock_kfree_s()
to free afterwards; less serious, but also needs fixing.

Patch by Al Viro, David Miller, David Woodhouse
(sparc64 clean compile fix from David Miller)

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Reassembly trim not clearing CHECKSUM_HW</title>
<updated>2005-09-10T02:42:52Z</updated>
<author>
<name>Stephen Hemminger</name>
<email>shemminger@osdl.org</email>
</author>
<published>2005-09-06T22:52:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cf43ea034180996242226eac042889c5b06c7df7'/>
<id>urn:sha1:cf43ea034180996242226eac042889c5b06c7df7</id>
<content type='text'>
[IPV4]: Reassembly trim not clearing CHECKSUM_HW

This was found by inspection while looking for checksum problems
with the skge driver that sets CHECKSUM_HW. It did not fix the
problem, but it looks like it is needed.

If IP reassembly is trimming an overlapping fragment, it
should reset (or adjust) the hardware checksum flag on the skb.

Signed-off-by: Stephen Hemminger &lt;shemminger@osdl.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] 2.6.13 breaks libpcap (and tcpdump)</title>
<updated>2005-09-10T02:42:51Z</updated>
<author>
<name>Herbert Xu</name>
<email>herbert@gondor.apana.org.au</email>
</author>
<published>2005-09-06T01:47:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a49567a4dbfd414f19e5bf828a4b2c540f164ea8'/>
<id>urn:sha1:a49567a4dbfd414f19e5bf828a4b2c540f164ea8</id>
<content type='text'>
[NET]: 2.6.13 breaks libpcap (and tcpdump)

Patrick McHardy says:

  Never mind, I got it, we never fall through to the second switch
  statement anymore. I think we could simply break when load_pointer
  returns NULL. The switch statement will fall through to the default
  case and return 0 for all cases but 0 &gt; k &gt;= SKF_AD_OFF.

Here's a patch to do just that.

I left BPF_MSH alone because it's really a hack to calculate the IP
header length, which makes no sense when applied to the special data.

Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@osdl.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[FIB_TRIE]: Don't ignore negative results from fib_semantic_match</title>
<updated>2005-08-24T05:06:09Z</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2005-08-24T05:06:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=06c7427021f1cc83703f14659d8405ca773ba1ef'/>
<id>urn:sha1:06c7427021f1cc83703f14659d8405ca773ba1ef</id>
<content type='text'>
When a semantic match occurs either success, not found or an error
(for matching unreachable routes/blackholes) is returned. fib_trie
ignores the errors and looks for a different matching route. Treat
results other than "no match" as success and end lookup.

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[ROSE]: Fix typo in rose_route_frame() locking fix.</title>
<updated>2005-08-23T21:55:32Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2005-08-23T21:55:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c1cc168442a943ed3997f6543db87c061987f9d7'/>
<id>urn:sha1:c1cc168442a943ed3997f6543db87c061987f9d7</id>
<content type='text'>
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[ROSE]: Fix missing unlocks in rose_route_frame()</title>
<updated>2005-08-23T17:50:09Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2005-08-23T17:50:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dc16aaf29d64b8c5e0b88f49a4d541edf5b61e42'/>
<id>urn:sha1:dc16aaf29d64b8c5e0b88f49a4d541edf5b61e42</id>
<content type='text'>
Noticed by Coverity checker.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[TCP]: Document non-trivial locking path in tcp_v{4,6}_get_port().</title>
<updated>2005-08-23T17:49:54Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2005-08-23T17:49:54Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d5d283751ef3c05b6766501a46800cbee84959d6'/>
<id>urn:sha1:d5d283751ef3c05b6766501a46800cbee84959d6</id>
<content type='text'>
This trips up a lot of folks reading this code.
Put an unlikely() around the port-exhaustion test
for good measure.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[TCP]: Unconditionally clear TCP_NAGLE_PUSH in skb_entail().</title>
<updated>2005-08-23T17:13:06Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2005-08-23T17:13:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=89ebd197eb2cd31d6187db344d5117064e19fdde'/>
<id>urn:sha1:89ebd197eb2cd31d6187db344d5117064e19fdde</id>
<content type='text'>
Intention of this bit is to force pushing of the existing
send queue when TCP_CORK or TCP_NODELAY state changes via
setsockopt().

But it's easy to create a situation where the bit never
clears.  For example, if the send queue starts empty:

1) set TCP_NODELAY
2) clear TCP_NODELAY
3) set TCP_CORK
4) do small write()

The current code will leave TCP_NAGLE_PUSH set after that
sequence.  Unconditionally clearing the bit when new data
is added via skb_entail() solves the problem.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
