linux-kernel - [ANNOUNCE] 3.12.0-rt1

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 10 Nov 2013 20:30:59 +0100
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	linux-rt-users <linux-rt-users@...r.kernel.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>, rostedt@...dmis.org,
	John Kacur <jkacur@...hat.com>
Subject: [ANNOUNCE] 3.12.0-rt1

Dear RT folks!

I'm pleased to announce the v3.12.0-rt1 patch set.

Changes since v3.10.18-rt14
- updated to v3.12
- dropped SLAB support. It was broken in v3.10 and therefore not available
  for RT. Nobody complained except that it did not compile on !RT. Since
  SLUB performs a little better compared to SLAB and is the default
  allocator I think it is okay to drop SLAB support.
- the PREEMPT_RT Kconfig patches are now very early in the queue.

This is the first release of the v3.12 kernel. It run a couple of days on
powerpc and x86 without an accident :)

Known issues:

      - bcache is disabled.

      - an ancient race (since we got sleeping spinlocks) where the
        TASK_TRACED state is temporary replaced while waiting on a rw
        lock and the task can't be traced.

The RT patch against 3.12 can be found here:

   https://www.kernel.org/pub/linux/kernel/projects/rt/3.10/3.12/patch-3.12.0-rt1.patch.xz

The split quilt queue is available at:

   https://www.kernel.org/pub/linux/kernel/projects/rt/3.10/3.12/patches-3.12.0-rt1.tar.xz

and it will be moved to the usual location once I able to do so.

Sebastian
--
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/