kernel news – 23.09.2012

Posted: September 23, 2012 in kernel

-Olof Johansson has ARM SoC fixes for -rc, Guenter Roeck updates hwmon for
-rc7, Dave Airlie updates drm for the big three – Intel, AMD and Nvidia, Ingo
Molnar updates per, timer and x86 with some fresh fixes, and David Miller
has two pull requests for SPARC and networking:

1) More kernel info leaks found by Mathias Krause, this time in the
IPSEC configuration layers.

2) When IPSEC policies change, we do not properly make sure that
cached routes (which could now be stale) throughout the system will
be revalidated. Fix this by generalizing the generation count
invalidation scheme used by ipv4. From Nicolas Dichtel.

3) When repairing TCP sockets, we need to allow to restore not just
the send window scale, but the receive one too. Extend the
existing interface to achieve this in a backwards compatible way.
From Andrey Vagin.

4) A fix for FCOE scatter gather feature validation erroneously
caused scatter gather to be disabled for things like AOE too.
From Ed L. Cashin.

5) Several cases of mishandling of error pointers, from Mathias Krause,
Wei Yongjun, and Devendra Naga.

6) Fix gianfar build, from Richard Cochran.

7) CAP_NET_* failures should return -EPERM not -EACCES, from Zhao

8) Hardware reset fix in janz-ican3 CAN driver, from Ira W. Snyder.

9) Fix oops during rmmod in ti_hecc CAN driver, from Marc Kleine-Budde.

10) The removal of the conditional compilation of the clk support code
in the stmmac driver broke things. This is because the interfaces
used are the ones that don’t also perform the enable/disable of
the clk. Fix from Stefan Roese.

11) The QFQ packet scheduler can record out of range virtual start
times, resulting later in misbehavior and even crashes. Fix
from Paolo Valente.

12) If MSG_WAITALL is used with IOAT DMA under TCP, we can wedge the
receiver when the advertised receive window goes to zero. Detect
this case and force the processing of the IOAT DMA queue when it
happens to avoid getting stuck. Fix from Michal Kubecek.

13) batman-adv assumes that test_bit() returns only 0 or 1, but this
is not true for x86 (which returns -1 or 0, via the ‘sbb’
instruction). Fix from Linus Lussing.

14) Fix small packet corruption in e1000, from Tushar Dave.

15) make_blackhole() in the IPSEC policy code can do one read unlock
too many, fix from Li RongQing.

16) The new tcp_try_coalesce() code introduced a bug in TCP URG handling,
fix from Eric Dumazet.

17) Fix memory leak in __netif_receive_skb() when doing zerocopy and
when hit an OOM condition. From Michael S. Tsirkin.

18) netxen blindly deferences pdev->bus->self, which is not guarenteed
to be non-NULL. Fix from Nikolay Aleksandrov.

19) Fix a performance regression caused by mistakes in ipv6 checksum
validation in the bnx2x driver, fix from Michal Schmidt.

-Jiri Kosina updates HID, with fixes related to Lenovo Thinkpad keyboards and
Logitech’s Unifying receiver, James Bottomley updates SCSI and Jown Linville
updates wireless:

For the Bluetooth bits, Gustavo says this:

“Here goes probably my last update to 3.6. It includes the two patches
you were ok last week(from Andrzej Kaczmarek), those are critical
ones, and two other fixes one for a system crash and the other for
a missing lockdep annotation.”

The referenced fixes from Andrzej prevent attempts to configure devices
that are powered-off.

Along with the Bluetooth fixes, there are a couple of 802.11 fixes.
Emmanuel Grumbach gives us an iwlwifi fix to prevent releasing an
interrupt twice. Luis R. Rodriguez provides a fix for a possible
circular lock dependency in the cfg80211 regulatory enforcement code.

All of these have been in linux-next for a few days. I hope they are
not too late to make the 3.6 release!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s