kernel news – 21.12.2012

-Chris Zankel has a Xtensa patchset, John W. Linville has
a wireless pull request

Gabor Juhos provides and rt2x00 fix to properly clear-out the skb->cb
for reporting tx_status. Recent changes made this necessary where it
previously was not.

Vladimir Kondratiev gives us a fix for a build issue that caused some
ath9k devices to be skipped in the build based on unrelated config
choices.

and Dave Airlie has a DRM fix related to Intel.

-David Miller and networking:

1) Really fix tuntap SKB use after free bug, from Eric Dumazet.

2) Adjust SKB data pointer to point past the transport header before
calling icmpv6_notify() so that the headers are in the state which
that function expects. From Duan Jiong.

3) Fix ambiguities in the new tuntap multi-queue APIs. From
Jason Wang.

4) mISDN needs to use del_timer_sync(), from Konstantin Khlebnikov.

5) Don’t destroy mutex after freeing up device private in mac802154,
fix also from Konstantin Khlebnikov.

6) Fix INET request socket leak in TCP and DCCP, from Christoph Paasch.

7) SCTP HMAC kconfig rework, from Neil Horman.

8) Fix SCTP jprobes function signature, otherwise things explode,
from Daniel Borkmann.

9) Fix typo in ipv6-offload Makefile variable reference, from
Simon Arlott.

10) Don’t fail USBNET open just because remote wakeup isn’t
supported, from Oliver Neukum.

11) be2net driver bug fixes from Sathya Perla.

12) SOLOS PCI ATM driver bug fixes from Nathan Williams and David
Woodhouse.

13) Fix MTU changing regression in 8139cp driver, from John Greene.

-The same David Miller updates SPARC, Takashi Iwai updates sound for -rc1,
Jesper Nilsson updates CRIS, there are IOMMU updates from Joerg Roedel,
and J. Bruce Fields has nfsd updates:

Included this time:

– more nfsd containerization work from Stanislav Kinsbursky: we’re not
quite there yet, but should be by 3.9.

– NFSv4.1 progress: implementation of basic backchannel security
negotiation and the mandatory BACKCHANNEL_CTL operation. See

http://wiki.linux-nfs.org/wiki/index.php/Server_4.0_and_4.1_issues

for remaining TODO’s

– Fixes for some bugs that could be triggered by unusual compounds.
Our xdr code wasn’t designed with v4 compounds in mind, and it
shows. A more thorough rewrite is still a todo.

– If you’ve ever seen “RPC: multiple fragments per record not
supported” logged while using some sort of odd userland NFS client,
that should now be fixed.

– Further work from Jeff Layton on our mechanism for storing
information about NFSv4 clients across reboots.

– Further work from Bryan Schumaker on his fault-injection mechanism
(which allows us to discard selective NFSv4 state, to excercise
rarely-taken recovery code paths in the client.)

– The usual mix of miscellaneous bugs and cleanup.

Thanks to everyone who tested or contributed this cycle.

-Sage Weil and Ceph:

There’s a trivial conflict in net/ceph/osd_client.c dealing with rbtree
node initialization; the resolution is to keep the RB_CLEAR_NODE() call
(see 4c199a93 for the conflicting commit).

There are a few different groups of commits here. The largest is Alex’s
ongoing work to enable the coming RBD features (cloning, striping).
There is some cleanup in libceph that goes along with it. Cyril and David
have fixed some problems with NFS reexport (leaking dentries and page
locks), and there is a batch of patches from Yan fixing problems with the
fs client when running against a clustered MDS. There are a few bug fixes
mixed in for good measure, many of which will be going to the stable trees
once they’re upstream.

My apologies for the late pull. There is still a gremlin in the rbd
map/unmap code and I was hoping to include the fix for that as well, but
we haven’t been able to confirm the fix is correct yet; I’ll send that in
a separate pull once it’s nailed down.

-Al Viro updates VFS and Eric Paris updates notify:

I believe you would get a build failure after this pull due to the
addition of procfs information for *notify fds. The attached patch from
sfr should be applied during the merge to change the spin_lock in that
patch to the mutex in this patch.

This pull mostly is about locking changes in the fsnotify system. By
switching the group lock from a spin_lock() to a mutex() we can now hold
the lock across things like iput(). This fixes a problem involving
unmounting a fs and having inodes be busy, first pointed out by FAT, but
reproducible with tmpfs.

This also restores signal driven I/O for inotify, which has been broken
since about 2.6.32.

-Wim van Sebroeck updates watchdog, and that’s it for now.