[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230514123254.GFZGDU9thNmJ4jmf7V@fat_crate.local>
Date: Sun, 14 May 2023 14:32:54 +0200
From: Borislav Petkov <bp@...en8.de>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: x86-ml <x86@...nel.org>, lkml <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] locking/urgent for v6.4-rc2
Hi Linus,
please pull a single urgent locking fix for 6.4.
Thx.
---
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/locking_urgent_for_v6.4_rc2
for you to fetch changes up to 92cc5d00a431e96e5a49c0b97e5ad4fa7536bd4b:
locking/rwsem: Add __always_inline annotation to __down_read_common() and inlined callers (2023-05-08 10:58:24 +0200)
----------------------------------------------------------------
- Make sure __down_read_common() is always inlined so that the callers'
names land in traceevents output instead and thus the blocked function
can be identified
----------------------------------------------------------------
John Stultz (1):
locking/rwsem: Add __always_inline annotation to __down_read_common() and inlined callers
kernel/locking/rwsem.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists