summaryrefslogtreecommitdiffstats
path: root/debian/patches-rt/0007-printk-use-seqcount_latch-for-clear_seq.patch
diff options
context:
space:
mode:
Diffstat (limited to 'debian/patches-rt/0007-printk-use-seqcount_latch-for-clear_seq.patch')
-rw-r--r--debian/patches-rt/0007-printk-use-seqcount_latch-for-clear_seq.patch2
1 files changed, 1 insertions, 1 deletions
diff --git a/debian/patches-rt/0007-printk-use-seqcount_latch-for-clear_seq.patch b/debian/patches-rt/0007-printk-use-seqcount_latch-for-clear_seq.patch
index 8371b8558..29c8b3fdb 100644
--- a/debian/patches-rt/0007-printk-use-seqcount_latch-for-clear_seq.patch
+++ b/debian/patches-rt/0007-printk-use-seqcount_latch-for-clear_seq.patch
@@ -1,7 +1,7 @@
From: John Ogness <john.ogness@linutronix.de>
Date: Mon, 30 Nov 2020 01:41:58 +0106
Subject: [PATCH 07/28] printk: use seqcount_latch for clear_seq
-Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/5.10/older/patches-5.10.17-rt32.tar.xz
+Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/5.10/older/patches-5.10.21-rt34.tar.xz
kmsg_dump_rewind_nolock() locklessly reads @clear_seq. However,
this is not done atomically. Since @clear_seq is 64-bit, this