<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/net, branch v3.14.8</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/net?h=v3.14.8</id>
<link rel='self' href='https://git.amat.us/linux/atom/net?h=v3.14.8'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-06-16T20:40:32Z</updated>
<entry>
<title>netfilter: ipv4: defrag: set local_df flag on defragmented skb</title>
<updated>2014-06-16T20:40:32Z</updated>
<author>
<name>Florian Westphal</name>
<email>fw@strlen.de</email>
</author>
<published>2014-05-02T13:32:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=806d009907bd86a03ecc7889e5794db74ba24ba6'/>
<id>urn:sha1:806d009907bd86a03ecc7889e5794db74ba24ba6</id>
<content type='text'>
commit 895162b1101b3ea5db08ca6822ae9672717efec0 upstream.

else we may fail to forward skb even if original fragments do fit
outgoing link mtu:

1. remote sends 2k packets in two 1000 byte frags, DF set
2. we want to forward but only see '2k &gt; mtu and DF set'
3. we then send icmp error saying that outgoing link is 1500

But original sender never sent a packet that would not fit
the outgoing link.

Setting local_df makes outgoing path test size vs.
IPCB(skb)-&gt;frag_max_size, so we will still send the correct
error in case the largest original size did not fit
outgoing link mtu.

Reported-by: Maxime Bizon &lt;mbizon@freebox.fr&gt;
Suggested-by: Maxime Bizon &lt;mbizon@freebox.fr&gt;
Fixes: 5f2d04f1f9 (ipv4: fix path MTU discovery with connection tracking)
Signed-off-by: Florian Westphal &lt;fw@strlen.de&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
Cc: Jiri Slaby &lt;jslaby@suse.cz&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>netfilter: nfnetlink: Fix use after free when it fails to process batch</title>
<updated>2014-06-11T18:54:14Z</updated>
<author>
<name>Denys Fedoryshchenko</name>
<email>nuclearcat@nuclearcat.com</email>
</author>
<published>2014-05-04T11:35:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=07e8687141e5073ff7931666982232bdc4bc3400'/>
<id>urn:sha1:07e8687141e5073ff7931666982232bdc4bc3400</id>
<content type='text'>
commit ecd15dd7e45f3683fa8142b9f2c015dfaa0c243d upstream.

This bug manifests when calling the nft command line tool without
nf_tables kernel support.

kernel message:
[   44.071555] Netfilter messages via NETLINK v0.30.
[   44.072253] BUG: unable to handle kernel NULL pointer dereference at 0000000000000119
[   44.072264] IP: [&lt;ffffffff8171db1f&gt;] netlink_getsockbyportid+0xf/0x70
[   44.072272] PGD 7f2b74067 PUD 7f2b73067 PMD 0
[   44.072277] Oops: 0000 [#1] SMP
[...]
[   44.072369] Call Trace:
[   44.072373]  [&lt;ffffffff8171fd81&gt;] netlink_unicast+0x91/0x200
[   44.072377]  [&lt;ffffffff817206c9&gt;] netlink_ack+0x99/0x110
[   44.072381]  [&lt;ffffffffa004b951&gt;] nfnetlink_rcv+0x3c1/0x408 [nfnetlink]
[   44.072385]  [&lt;ffffffff8171fde3&gt;] netlink_unicast+0xf3/0x200
[   44.072389]  [&lt;ffffffff817201ef&gt;] netlink_sendmsg+0x2ff/0x740
[   44.072394]  [&lt;ffffffff81044752&gt;] ? __mmdrop+0x62/0x90
[   44.072398]  [&lt;ffffffff816dafdb&gt;] sock_sendmsg+0x8b/0xc0
[   44.072403]  [&lt;ffffffff812f1af5&gt;] ? copy_user_enhanced_fast_string+0x5/0x10
[   44.072406]  [&lt;ffffffff816dbb6c&gt;] ? move_addr_to_kernel+0x2c/0x50
[   44.072410]  [&lt;ffffffff816db423&gt;] ___sys_sendmsg+0x3c3/0x3d0
[   44.072415]  [&lt;ffffffff811301ba&gt;] ? handle_mm_fault+0xa9a/0xc60
[   44.072420]  [&lt;ffffffff811362d6&gt;] ? mmap_region+0x166/0x5a0
[   44.072424]  [&lt;ffffffff817da84c&gt;] ? __do_page_fault+0x1dc/0x510
[   44.072428]  [&lt;ffffffff812b8b2c&gt;] ? apparmor_capable+0x1c/0x60
[   44.072435]  [&lt;ffffffff817d6e9a&gt;] ? _raw_spin_unlock_bh+0x1a/0x20
[   44.072439]  [&lt;ffffffff816dfc86&gt;] ? release_sock+0x106/0x150
[   44.072443]  [&lt;ffffffff816dc212&gt;] __sys_sendmsg+0x42/0x80
[   44.072446]  [&lt;ffffffff816dc262&gt;] SyS_sendmsg+0x12/0x20
[   44.072450]  [&lt;ffffffff817df616&gt;] system_call_fastpath+0x1a/0x1f

Signed-off-by: Denys Fedoryshchenko &lt;nuclearcat@nuclearcat.com&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>netfilter: Fix potential use after free in ip6_route_me_harder()</title>
<updated>2014-06-11T18:54:14Z</updated>
<author>
<name>Sergey Popovich</name>
<email>popovich_sergei@mail.ru</email>
</author>
<published>2014-05-08T13:22:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=64db35627759552fe11de45d3787737a6fe9a3af'/>
<id>urn:sha1:64db35627759552fe11de45d3787737a6fe9a3af</id>
<content type='text'>
commit a8951d5814e1373807a94f79f7ccec7041325470 upstream.

Dst is released one line before we access it again with dst-&gt;error.

Fixes: 58e35d147128 netfilter: ipv6: propagate routing errors from
ip6_route_me_harder()

Signed-off-by: Sergey Popovich &lt;popovich_sergei@mail.ru&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Bluetooth: Fix L2CAP LE debugfs entries permissions</title>
<updated>2014-06-11T18:54:12Z</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2014-05-14T15:53:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=777b5819a2994320f98ee377b6196b1660e12bb6'/>
<id>urn:sha1:777b5819a2994320f98ee377b6196b1660e12bb6</id>
<content type='text'>
commit 40b9397a1a61a37917b93e7d57e6f2faf3a086b4 upstream.

0466 was probably meant to be 0644, there's no reason why everyone
except root could write there.

Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>libceph: fix corruption when using page_count 0 page in rbd</title>
<updated>2014-06-07T17:28:28Z</updated>
<author>
<name>Chunwei Chen</name>
<email>tuxoko@gmail.com</email>
</author>
<published>2014-04-23T04:35:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=bcd5faf938fb061c4c02874a906b68c5642822f3'/>
<id>urn:sha1:bcd5faf938fb061c4c02874a906b68c5642822f3</id>
<content type='text'>
commit 178eda29ca721842f2146378e73d43e0044c4166 upstream.

It has been reported that using ZFSonLinux on rbd will result in memory
corruption. The bug report can be found here:

https://github.com/zfsonlinux/spl/issues/241
http://tracker.ceph.com/issues/7790

The reason is that ZFS will send pages with page_count 0 into rbd, which in
turns send them to tcp_sendpage. However, tcp_sendpage cannot deal with
page_count 0, as it will do get_page and put_page, and erroneously free the
page.

This type of issue has been noted before, and handled in iscsi, drbd,
etc. So, rbd should also handle this. This fix address this issue by fall back
to slower sendmsg when page_count 0 detected.

Cc: Sage Weil &lt;sage@inktank.com&gt;
Cc: Yehuda Sadeh &lt;yehuda@inktank.com&gt;
Signed-off-by: Chunwei Chen &lt;tuxoko@gmail.com&gt;
Reviewed-by: Ilya Dryomov &lt;ilya.dryomov@inktank.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Bluetooth: Fix redundant encryption request for reauthentication</title>
<updated>2014-06-07T17:28:16Z</updated>
<author>
<name>Johan Hedberg</name>
<email>johan.hedberg@intel.com</email>
</author>
<published>2014-04-11T19:02:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=fe8578f3e20633647165faf324f283e67deff7e5'/>
<id>urn:sha1:fe8578f3e20633647165faf324f283e67deff7e5</id>
<content type='text'>
commit 09da1f3463eb81d59685df723b1c5950b7570340 upstream.

When we're performing reauthentication (in order to elevate the
security level from an unauthenticated key to an authenticated one) we
do not need to issue any encryption command once authentication
completes. Since the trigger for the encryption HCI command is the
ENCRYPT_PEND flag this flag should not be set in this scenario.
Instead, the REAUTH_PEND flag takes care of all necessary steps for
reauthentication.

Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Bluetooth: Fix triggering BR/EDR L2CAP Connect too early</title>
<updated>2014-06-07T17:28:16Z</updated>
<author>
<name>Johan Hedberg</name>
<email>johan.hedberg@intel.com</email>
</author>
<published>2014-04-11T19:02:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5e3ccae03cc3a26f535067c26e8f65d46679302f'/>
<id>urn:sha1:5e3ccae03cc3a26f535067c26e8f65d46679302f</id>
<content type='text'>
commit 9eb1fbfa0a737fd4d3a6d12d71c5ea9af622b887 upstream.

Commit 1c2e004183178 introduced an event handler for the encryption key
refresh complete event with the intent of fixing some LE/SMP cases.
However, this event is shared with BR/EDR and there we actually want to
act only on the auth_complete event (which comes after the key refresh).

If we do not do this we may trigger an L2CAP Connect Request too early
and cause the remote side to return a security block error.

Signed-off-by: Johan Hedberg &lt;johan.hedberg@intel.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>mac80211: fix on-channel remain-on-channel</title>
<updated>2014-06-07T17:28:10Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2014-05-14T13:34:41Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6a12f896ce0aa2e88af62b5282b2a40488a5283e'/>
<id>urn:sha1:6a12f896ce0aa2e88af62b5282b2a40488a5283e</id>
<content type='text'>
commit b4b177a5556a686909e643f1e9b6434c10de079f upstream.

Jouni reported that if a remain-on-channel was active on the
same channel as the current operating channel, then the ROC
would start, but any frames transmitted using mgmt-tx on the
same channel would get delayed until after the ROC.

The reason for this is that the ROC starts, but doesn't have
any handling for "remain on the same channel", so it stops
the interface queues. The later mgmt-tx then puts the frame
on the interface queues (since it's on the current operating
channel) and thus they get delayed until after the ROC.

To fix this, add some logic to handle remaining on the same
channel specially and not stop the queues etc. in this case.
This not only fixes the bug but also improves behaviour in
this case as data frames etc. can continue to flow.

Reported-by: Jouni Malinen &lt;j@w1.fi&gt;
Tested-by: Jouni Malinen &lt;j@w1.fi&gt;
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>mac80211: fix suspend vs. association race</title>
<updated>2014-06-07T17:28:10Z</updated>
<author>
<name>Emmanuel Grumbach</name>
<email>emmanuel.grumbach@intel.com</email>
</author>
<published>2014-05-13T09:54:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=802cb37dbc7b07bb557ca7a9817c1566e28c8d26'/>
<id>urn:sha1:802cb37dbc7b07bb557ca7a9817c1566e28c8d26</id>
<content type='text'>
commit c52666aef9f2dff39276eb53f15d99e2e229870f upstream.

If the association is in progress while we suspend, the
stack will be in a messed up state. Clean it before we
suspend.

This patch completes Johannes's patch:

1a1cb744de160ee70086a77afff605bbc275d291
Author: Johannes Berg &lt;johannes.berg@intel.com&gt;

    mac80211: fix suspend vs. authentication race

Fixes: 12e7f517029d ("mac80211: cleanup generic suspend/resume procedures")
Signed-off-by: Emmanuel Grumbach &lt;emmanuel.grumbach@intel.com&gt;
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>mac80211: fix nested rtnl locking on ieee80211_reconfig</title>
<updated>2014-06-07T17:28:10Z</updated>
<author>
<name>Eliad Peller</name>
<email>eliad@wizery.com</email>
</author>
<published>2014-04-30T13:14:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8faa53c451ac66d604253105b2041356d723d4c1'/>
<id>urn:sha1:8faa53c451ac66d604253105b2041356d723d4c1</id>
<content type='text'>
commit e669ba2d06c6195662601956454ac959892f0762 upstream.

ieee80211_reconfig already holds rtnl, so calling
cfg80211_sched_scan_stopped results in deadlock.

Use the rtnl-version of this function instead.

Fixes: d43c6b6 ("mac80211: reschedule sched scan after HW restart")
Signed-off-by: Eliad Peller &lt;eliadx.peller@intel.com&gt;
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
</feed>
