linux-kernel - Linux 2.6.37-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 1 Nov 2010 08:07:50 -0400
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Linux 2.6.37-rc1

The merge window for 2.6.37 is over, and -rc1 is out there (or will be
soon, as things are uploading from my laptop here in Boston and then
mirroring out)

There's a lot of changes there - just shy of 10k commits since 2.6.36
- despite the slightly shortened merge window. Way too many to list.
But the part that I think deserves some extra mention is that we've
finally largely gotten rid of the BKL (big kernel lock) in all the
core stuff, and you can easily compile a kernel without any BKL
support at all. It's been a long road, and thanks to Arnd and others
who did it.

Note that "core code" does not mean "everything". There are still
drivers out there that need the BKL, and if you configure the kernel
without it, you won't be able to configure in the V4L drivers, for
example. They still have lock_kernel/unlock_kernel calls in them, but
hopefully that will get fixed too, to the point where in the not too
distant future we will hopefully see only some legacy drivers that
nobody uses needing the old locking.

Other than that, it looks like a fairly normal release. Lots of
changes all over, with drivers - as usual - dominating the patches.
Give it all a try, and hopefully this will be a quiet week wrt
development with lots of core developers here at the kernel summit.

                           Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/