<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/net, branch v3.1</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/net?h=v3.1</id>
<link rel='self' href='https://git.amat.us/linux/atom/net?h=v3.1'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-10-19T23:17:41Z</updated>
<entry>
<title>fib_rules: fix unresolved_rules counting</title>
<updated>2011-10-19T23:17:41Z</updated>
<author>
<name>Yan, Zheng</name>
<email>zheng.z.yan@intel.com</email>
</author>
<published>2011-10-17T15:20:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=afaef734e5f0004916d07ecf7d86292cdd00d59b'/>
<id>urn:sha1:afaef734e5f0004916d07ecf7d86292cdd00d59b</id>
<content type='text'>
we should decrease ops-&gt;unresolved_rules when deleting a unresolved rule.

Signed-off-by: Zheng Yan &lt;zheng.z.yan@intel.com&gt;
Acked-by: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>tproxy: copy transparent flag when creating a time wait</title>
<updated>2011-10-19T07:21:35Z</updated>
<author>
<name>KOVACS Krisztian</name>
<email>hidden@balabit.hu</email>
</author>
<published>2011-10-18T10:17:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=58af19e387d8821927e49be3f467da5e6a0aa8fd'/>
<id>urn:sha1:58af19e387d8821927e49be3f467da5e6a0aa8fd</id>
<content type='text'>
The transparent socket option setting was not copied to the time wait
socket when an inet socket was being replaced by a time wait socket. This
broke the --transparent option of the socket match and may have caused
that FIN packets belonging to sockets in FIN_WAIT2 or TIME_WAIT state
were being dropped by the packet filter.

Signed-off-by: KOVACS Krisztian &lt;hidden@balabit.hu&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>bluetooth: Properly clone LSM attributes to newly created child connections</title>
<updated>2011-10-19T03:36:43Z</updated>
<author>
<name>Paul Moore</name>
<email>pmoore@redhat.com</email>
</author>
<published>2011-10-07T09:40:59Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6230c9b4f8957c8938ee4cf2d03166d3c2dc89de'/>
<id>urn:sha1:6230c9b4f8957c8938ee4cf2d03166d3c2dc89de</id>
<content type='text'>
The Bluetooth stack has internal connection handlers for all of the various
Bluetooth protocols, and unfortunately, they are currently lacking the LSM
hooks found in the core network stack's connection handlers.  I say
unfortunately, because this can cause problems for users who have have an
LSM enabled and are using certain Bluetooth devices.  See one problem
report below:

 * http://bugzilla.redhat.com/show_bug.cgi?id=741703

In order to keep things simple at this point in time, this patch fixes the
problem by cloning the parent socket's LSM attributes to the newly created
child socket.  If we decide we need a more elaborate LSM marking mechanism
for Bluetooth (I somewhat doubt this) we can always revisit this decision
in the future.

Reported-by: James M. Cape &lt;jcape@ignore-your.tv&gt;
Signed-off-by: Paul Moore &lt;pmoore@redhat.com&gt;
Acked-by: James Morris &lt;jmorris@namei.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>l2tp: fix a potential skb leak in l2tp_xmit_skb()</title>
<updated>2011-10-19T03:32:00Z</updated>
<author>
<name>Eric Dumazet</name>
<email>eric.dumazet@gmail.com</email>
</author>
<published>2011-10-07T05:35:46Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=835acf5da239b91edb9f7ebe36516999e156e6ee'/>
<id>urn:sha1:835acf5da239b91edb9f7ebe36516999e156e6ee</id>
<content type='text'>
l2tp_xmit_skb() can leak one skb if skb_cow_head() returns an error.

Signed-off-by: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>bridge: fix hang on removal of bridge via netlink</title>
<updated>2011-10-19T03:24:16Z</updated>
<author>
<name>stephen hemminger</name>
<email>shemminger@vyatta.com</email>
</author>
<published>2011-10-06T11:19:41Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1ce5cce895309862d2c35d922816adebe094fe4a'/>
<id>urn:sha1:1ce5cce895309862d2c35d922816adebe094fe4a</id>
<content type='text'>
Need to cleanup bridge device timers and ports when being bridge
device is being removed via netlink.

This fixes the problem of observed when doing:
 ip link add br0 type bridge
 ip link set dev eth1 master br0
 ip link set br0 up
 ip link del br0

which would cause br0 to hang in unregister_netdev because
of leftover reference count.

Reported-by: Sridhar Samudrala &lt;sri@us.ibm.com&gt;
Signed-off-by: Stephen Hemminger &lt;shemminger@vyatta.com&gt;
Acked-by: Sridhar Samudrala &lt;sri@us.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge branch 'nf' of git://1984.lsi.us.es/net</title>
<updated>2011-10-17T23:38:03Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2011-10-17T23:38:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ae2a4583154a5b985ed4a81c6259c55bafe6d810'/>
<id>urn:sha1:ae2a4583154a5b985ed4a81c6259c55bafe6d810</id>
<content type='text'>
</content>
</entry>
<entry>
<title>x25: Prevent skb overreads when checking call user data</title>
<updated>2011-10-17T23:31:40Z</updated>
<author>
<name>Matthew Daley</name>
<email>mattjd@gmail.com</email>
</author>
<published>2011-10-14T18:45:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7f81e25befdfb3272345a2e775f520e1d515fa20'/>
<id>urn:sha1:7f81e25befdfb3272345a2e775f520e1d515fa20</id>
<content type='text'>
x25_find_listener does not check that the amount of call user data given
in the skb is big enough in per-socket comparisons, hence buffer
overreads may occur.  Fix this by adding a check.

Signed-off-by: Matthew Daley &lt;mattjd@gmail.com&gt;
Cc: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Cc: Andrew Hendry &lt;andrew.hendry@gmail.com&gt;
Cc: stable &lt;stable@kernel.org&gt;
Acked-by: Andrew Hendry &lt;andrew.hendry@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>x25: Handle undersized/fragmented skbs</title>
<updated>2011-10-17T23:31:39Z</updated>
<author>
<name>Matthew Daley</name>
<email>mattjd@gmail.com</email>
</author>
<published>2011-10-14T18:45:04Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cb101ed2c3c7c0224d16953fe77bfb9d6c2cb9df'/>
<id>urn:sha1:cb101ed2c3c7c0224d16953fe77bfb9d6c2cb9df</id>
<content type='text'>
There are multiple locations in the X.25 packet layer where a skb is
assumed to be of at least a certain size and that all its data is
currently available at skb-&gt;data.  These assumptions are not checked,
hence buffer overreads may occur.  Use pskb_may_pull to check these
minimal size assumptions and ensure that data is available at skb-&gt;data
when necessary, as well as use skb_copy_bits where needed.

Signed-off-by: Matthew Daley &lt;mattjd@gmail.com&gt;
Cc: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Cc: Andrew Hendry &lt;andrew.hendry@gmail.com&gt;
Cc: stable &lt;stable@kernel.org&gt;
Acked-by: Andrew Hendry &lt;andrew.hendry@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>x25: Validate incoming call user data lengths</title>
<updated>2011-10-17T23:31:39Z</updated>
<author>
<name>Matthew Daley</name>
<email>mattjd@gmail.com</email>
</author>
<published>2011-10-14T18:45:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c7fd0d48bde943e228e9c28ce971a22d6a1744c4'/>
<id>urn:sha1:c7fd0d48bde943e228e9c28ce971a22d6a1744c4</id>
<content type='text'>
X.25 call user data is being copied in its entirety from incoming messages
without consideration to the size of the destination buffers, leading to
possible buffer overflows. Validate incoming call user data lengths before
these copies are performed.

It appears this issue was noticed some time ago, however nothing seemed to
come of it: see http://www.spinics.net/lists/linux-x25/msg00043.html and
commit 8db09f26f912f7c90c764806e804b558da520d4f.

Signed-off-by: Matthew Daley &lt;mattjd@gmail.com&gt;
Acked-by: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Tested-by: Andrew Hendry &lt;andrew.hendry@gmail.com&gt;
Cc: stable &lt;stable@kernel.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>IPVS netns shutdown/startup dead-lock</title>
<updated>2011-10-12T16:32:15Z</updated>
<author>
<name>Hans Schillstrom</name>
<email>hans@schillstrom.com</email>
</author>
<published>2011-10-11T01:54:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ae1d48b23d5e79efbcf0cef4f0ebb9742361af59'/>
<id>urn:sha1:ae1d48b23d5e79efbcf0cef4f0ebb9742361af59</id>
<content type='text'>
ip_vs_mutext is used by both netns shutdown code and startup
and both implicit uses sk_lock-AF_INET mutex.

cleanup CPU-1         startup CPU-2
ip_vs_dst_event()     ip_vs_genl_set_cmd()
 sk_lock-AF_INET     __ip_vs_mutex
                     sk_lock-AF_INET
__ip_vs_mutex
* DEAD LOCK *

A new mutex placed in ip_vs netns struct called sync_mutex is added.

Comments from Julian and Simon added.
This patch has been running for more than 3 month now and it seems to work.

Ver. 3
    IP_VS_SO_GET_DAEMON in do_ip_vs_get_ctl protected by sync_mutex
    instead of __ip_vs_mutex as sugested by Julian.

Signed-off-by: Hans Schillstrom &lt;hans@schillstrom.com&gt;
Acked-by: Julian Anastasov &lt;ja@ssi.bg&gt;
Signed-off-by: Simon Horman &lt;horms@verge.net.au&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
</content>
</entry>
</feed>
