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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Fri, 21 Mar 2014 21:13:53 +0100
From:	Sebastian Andrzej Siewior <>
To:	linux-rt-users <>
Cc:	LKML <>,
	Thomas Gleixner <>,,
	John Kacur <>
Subject: [ANNOUNCE] 3.12.14-rt23

Dear RT folks!

I'm pleased to announce the v3.12.14-rt23 patch set.

Changes since v3.12.14-rt22
- Helmut Buchsbaum run into OOM because RCU did not have enough time to
  free memory. The problem appeared while the RCU softirq has been
  replaced by the RCU thread. The problem can be "fixed" by giving a
  higher priority to the RCU thread or by just enabled the "RCU_BOOST"
  kernel option. The kernel option is now enabled by default on an -RT
  enabled system and can be disabled by the user if desired.

Known issues:

      - bcache is disabled.

The delta patch against v3.12.14-rt22 is appended below and can be found

The RT patch against 3.12.14 can be found here:

The split quilt queue is available at:


diff --git a/init/Kconfig b/init/Kconfig
index 4dea595..f6aeea6 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -642,7 +642,7 @@ config TREE_RCU_TRACE
 config RCU_BOOST
 	bool "Enable RCU priority boosting"
 	depends on RT_MUTEXES && PREEMPT_RCU
-	default n
+	default y if PREEMPT_RT_FULL
 	  This option boosts the priority of preempted RCU readers that
 	  block the current preemptible RCU grace period for too long.
diff --git a/localversion-rt b/localversion-rt
index c29508d..9a218ca 100644
--- a/localversion-rt
+++ b/localversion-rt
@@ -1 +1 @@
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists