From: Will Deacon <will.deacon@arm.com>
To: linux-kernel@vger.kernel.org
Cc: sebott@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, peterz@infradead.org,
mingo@kernel.org, Will Deacon <will.deacon@arm.com>
Subject: [PATCH 0/2] Fix boot regression for s390 and remove break_lock
Date: Tue, 28 Nov 2017 18:42:17 +0000 [thread overview]
Message-ID: <1511894539-7988-1-git-send-email-will.deacon@arm.com> (raw)
Hi all,
The following two patches do the following:
1. Fix boot breakage reported on s390 caused by a8a217c22116
2. Kill off the break_lock field entirely, since it's not actually
that useful
I didn't go the whole hog and remove CONFIG_GENERIC_LOCKBREAK, since the
"do something different with locks in preemptible kernels" isn't necessarily
a bad idea, and PowerPC actually implements things like arch_spin_relax
for that.
The first patch should go in to 4.15.
Thanks,
Will
--->8
Will Deacon (2):
locking/core: Fix deadlock during boot on systems with
GENERIC_LOCKBREAK
locking/core: Remove break_lock field when CONFIG_GENERIC_LOCKBREAK=y
include/linux/rwlock_types.h | 3 ---
include/linux/spinlock.h | 5 -----
include/linux/spinlock_types.h | 3 ---
kernel/locking/spinlock.c | 13 +++----------
4 files changed, 3 insertions(+), 21 deletions(-)
--
2.1.4
next reply other threads:[~2017-11-28 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 18:42 Will Deacon [this message]
2017-11-28 18:42 ` [PATCH 1/2] locking/core: Fix deadlock during boot on systems with GENERIC_LOCKBREAK Will Deacon
2017-12-12 10:58 ` [tip:locking/urgent] " tip-bot for Will Deacon
2017-11-28 18:42 ` [PATCH 2/2] locking/core: Remove break_lock field when CONFIG_GENERIC_LOCKBREAK=y Will Deacon
2017-12-12 10:58 ` [tip:locking/urgent] " tip-bot for Will Deacon
2017-12-02 9:02 ` [PATCH 0/2] Fix boot regression for s390 and remove break_lock Heiko Carstens
2017-12-11 12:47 ` Will Deacon
2017-12-11 14:02 ` Ingo Molnar
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=1511894539-7988-1-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).