<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/net, branch v2.6.14.5</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/net?h=v2.6.14.5</id>
<link rel='self' href='https://git.amat.us/linux/atom/net?h=v2.6.14.5'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2005-12-27T00:08:58Z</updated>
<entry>
<title>[PATCH] Perform SA switchover immediately.</title>
<updated>2005-12-27T00:08:58Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2005-12-20T01:03:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5bc50c7bd333ab656acc16c1539c29d3d9a65600'/>
<id>urn:sha1:5bc50c7bd333ab656acc16c1539c29d3d9a65600</id>
<content type='text'>
When we insert a new xfrm_state which potentially
subsumes an existing one, make sure all cached
bundles are flushed so that the new SA is used
immediately.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix route lifetime.</title>
<updated>2005-12-27T00:08:58Z</updated>
<author>
<name>YOSHIFUJI Hideaki</name>
<email>yoshfuji@linux-ipv6.org</email>
</author>
<published>2005-12-20T01:01:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=974674b84fe907035254bc0a5257a4e1c511f156'/>
<id>urn:sha1:974674b84fe907035254bc0a5257a4e1c511f156</id>
<content type='text'>
The route expiration time is stored in rt6i_expires in jiffies.
The argument of rt6_route_add() for adding a route is not the
expiration time in jiffies nor in clock_t, but the lifetime
(or time left before expiration) in clock_t.

Because of the confusion, we sometimes saw several strange errors
(FAILs) in TAHI IPv6 Ready Logo Phase-2 Self Test.
The symptoms were analyzed by Mitsuru Chinen &lt;CHINEN@jp.ibm.com&gt;.

Signed-off-by: YOSHIFUJI Hideaki &lt;yoshfuji@linux-ipv6.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix bridge-nf ipv6 length check</title>
<updated>2005-12-27T00:08:57Z</updated>
<author>
<name>Bart De Schuymer</name>
<email>bdschuym@pandora.be</email>
</author>
<published>2005-12-20T01:00:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a7508849e7d21b89010539d54359ef8f3d89e8ec'/>
<id>urn:sha1:a7508849e7d21b89010539d54359ef8f3d89e8ec</id>
<content type='text'>
A typo caused some bridged IPv6 packets to get dropped randomly,
as reported by Sebastien Chaumontet. The patch below fixes this
(using skb-&gt;nh.raw instead of raw) and also makes the jumbo packet
length checking up-to-date with the code in
net/ipv6/exthdrs.c::ipv6_hop_jumbo.

Signed-off-by: Bart De Schuymer &lt;bdschuym@pandora.be&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix incorrect dependency for IP6_NF_TARGET_NFQUEUE</title>
<updated>2005-12-27T00:08:57Z</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2005-12-20T00:58:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d7709473c4a79ea3e90a8e44d81733ec2dc302de'/>
<id>urn:sha1:d7709473c4a79ea3e90a8e44d81733ec2dc302de</id>
<content type='text'>
IP6_NF_TARGET_NFQUEUE depends on IP6_NF_IPTABLES, not IP_NF_IPTABLES.

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix NAT init order</title>
<updated>2005-12-27T00:08:57Z</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2005-12-20T00:57:21Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9eda9ffc608c2a200754905ceeb68fda1d2b5873'/>
<id>urn:sha1:9eda9ffc608c2a200754905ceeb68fda1d2b5873</id>
<content type='text'>
As noticed by Phil Oester, the GRE NAT protocol helper is initialized
before the NAT core, which makes registration fail.

Change the linking order to make NAT be initialized first.

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix hardware rx csum errors</title>
<updated>2005-12-27T00:08:56Z</updated>
<author>
<name>Stephen Hemminger</name>
<email>shemminger@osdl.org</email>
</author>
<published>2005-12-15T00:29:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ed67d6e838c2203a64d815596e400822d5283875'/>
<id>urn:sha1:ed67d6e838c2203a64d815596e400822d5283875</id>
<content type='text'>
Receiving VLAN packets over a device (without VLAN assist) that is
doing hardware checksumming (CHECKSUM_HW), causes errors because the
VLAN code forgets to adjust the hardware checksum.

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@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix hardware checksum modification</title>
<updated>2005-12-27T00:08:56Z</updated>
<author>
<name>Herbert Xu</name>
<email>herbert@gondor.apana.org.au</email>
</author>
<published>2005-12-14T21:02:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=53e2254fe13b88de5957b22a5264e8e01e599f51'/>
<id>urn:sha1:53e2254fe13b88de5957b22a5264e8e01e599f51</id>
<content type='text'>
The skb_postpull_rcsum introduced a bug to the checksum modification.
Although the length pulled is offset bytes, the origin of the pulling
is the GRE header, not the IP header.

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@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix unbalanced read_unlock_bh in ctnetlink</title>
<updated>2005-12-27T00:08:55Z</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2005-12-13T11:26:07Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b72c1d0c14634506a2ff740033ab1bda3c3d5d7f'/>
<id>urn:sha1:b72c1d0c14634506a2ff740033ab1bda3c3d5d7f</id>
<content type='text'>
NFA_NEST calls NFA_PUT which jumps to nfattr_failure if the skb has no
room left. We call read_unlock_bh at nfattr_failure for the NFA_PUT
inside the locked section, so move NFA_NEST inside the locked section
too.

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Krzysztof Piotr Oledzki &lt;ole@ans.pl&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] Fix CTA_PROTO_NUM attribute size in ctnetlink</title>
<updated>2005-12-27T00:08:55Z</updated>
<author>
<name>Krzysztof Oledzki</name>
<email>olenf@ans.pl</email>
</author>
<published>2005-12-13T09:56:08Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1e7d00170b9215692eee2628c2a7d6af86cabfa7'/>
<id>urn:sha1:1e7d00170b9215692eee2628c2a7d6af86cabfa7</id>
<content type='text'>
CTA_PROTO_NUM is a u_int8_t.

Based on oryginal patch by Patrick McHardy &lt;kaber@trash.net&gt;

Signed-off-by: Krzysztof Piotr Oledzki &lt;ole@ans.pl&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>[PATCH] BRIDGE: recompute features when adding a new device</title>
<updated>2005-12-14T23:42:59Z</updated>
<author>
<name>Olaf Rempel</name>
<email>razzor@kopf-tisch.de</email>
</author>
<published>2005-11-24T08:00:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=51adb32b28e76270e850235a9f61c8379376be51'/>
<id>urn:sha1:51adb32b28e76270e850235a9f61c8379376be51</id>
<content type='text'>
[BRIDGE]: recompute features when adding a new device

We must recompute bridge features everytime the list of underlying
devices changes, or we might end up with features that are not supported
by all devices (eg. NETIF_F_TSO)
This patch adds the missing recompute when adding a device to the bridge.

Signed-off-by: Olaf Rempel &lt;razzor@kopf-tisch.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
</feed>
