kernel news – 01.02.2013

Posted: February 1, 2013 in kernel

-Trond Myklebust has NFS client fixes:

– Error reporting in nfs_xdev_mount incorrectly maps all errors to ENOMEM
– Fix an NFSv4 refcounting issue
– Fix a mount failure when the server reboots during NFSv4 trunking discovery
– NFSv4.1 mounts may need to run the lease recovery thread.
– Don’t silently fail setattr() requests on mountpoints
– Fix a SUNRPC socket/transport livelock and priority queue issue
– We must handle NFS4ERR_DELAY when resetting the NFSv4.1 session.

-Jiri Kosina and HID:

– fix i2c-hid and hidraw interaction, by Benjamin Tissoires
– a quirk to make a particular device (Formosa IR receiver) work properly,
by Nicholas Santos

-Linus Torvalds announces kernel 3.8-rc6:

It’s been a week since -rc5 (perhaps not counting timezone changes),
so -rc6 is out now.

I have to say, -rc6 is bigger than I’d like it to be. I’d really like
things to calm down by rc6, because usually I aim for rc7 to be
roughly the last rc in the series, and that means that I don’t want to
see hundreds of patches. But hundreds of patches it is. Not good.

That said, I’m hoping that the bulk of this was due to Davem catching
the flu and the networking pull being delayed by that. Because while
there’s been a few other worrisome patterns (x86 changes, EFI stuff
etc), it is largely true that a lot of the rc6 patches were

So I’m hoping that rc7 would be better quite quite on its own.

But since I don’t trust you sneaky bastards, I have a CleverPlan(tm)
to make *sure* that rc7 will be better and much smaller. That plan
largely depends on me being unreachable for the next week due to the
fact that there is no internet under water.

Paraphrasing the Alien films: “Under water, nobody can read your email”.

And once I dry off enough, I’m going to be really pissy (“And how is
that different from the normal Linus, pray tell?”) if people send me
pull requests that I think you shouldn’t have sent. There will be
cursing. More cursing than normal. Don’t send me stuff that doesn’t
fix major security issues, big user-reported regressions, or nasty
oopses. Seriously. Just don’t.

So think twice – or thrice – before sending me patches or a pull
request for -rc7. You need to have some seriously good reasons for
doing so, and you need to state those reasons very clearly. And I
don’t just mean for the pull request in general, I mean for every
single patch in it. So don’t ask me to pull three patches, because
_one_ of the three patches fixes a bad regression. Because while I can
see myself doing an rc8 (and I may just have to), I’m not going to
enjoy it much. So please help make sure that rc7 really is tiny and
only contains fixed that absolutely *have* to go in.

In other words, “It fixes a bug” just isn’t good enough. The bug needs
to be something that actually matters.


-James Morris has a small linux-security fix (memory leak), Arnaldo
Carvalho de Melo has perf/core fixes, and that’s all for now.


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 )

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s