From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] locking/urgent for v5.9-rc6
Date: Sun, 20 Sep 2020 21:51:20 +0200 [thread overview]
Message-ID: <20200920195120.GE13044@zn.tnic> (raw)
Hi Linus,
please pull two fixes from the locking/urgent pile.
Thx.
---
The following changes since commit fc3abb53250a90ba2150eebd182137c136f4d25a:
Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid (2020-09-02 12:55:46 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/locking_urgent_for_v5.9_rc6
for you to fetch changes up to e6b1a44eccfcab5e5e280be376f65478c3b2c7a2:
locking/percpu-rwsem: Use this_cpu_{inc,dec}() for read_count (2020-09-16 16:26:56 +0200)
----------------------------------------------------------------
* Fix lockdep's detection of "USED" <- "IN-NMI" inversions, from Peter
Zijlstra.
* Make percpu-rwsem operations on the semaphore's ->read_count IRQ-safe
because it can be used in an IRQ context, from Hou Tao.
----------------------------------------------------------------
Hou Tao (1):
locking/percpu-rwsem: Use this_cpu_{inc,dec}() for read_count
peterz@infradead.org (1):
locking/lockdep: Fix "USED" <- "IN-NMI" inversions
include/linux/percpu-rwsem.h | 8 ++++----
kernel/locking/lockdep.c | 35 +++++++++++++++++++++++++++++------
kernel/locking/lockdep_internals.h | 2 ++
kernel/locking/percpu-rwsem.c | 4 ++--
4 files changed, 37 insertions(+), 12 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next reply other threads:[~2020-09-20 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 19:51 Borislav Petkov [this message]
2020-09-20 22:40 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200920195120.GE13044@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®