From: Coly Li <colyli@suse.de>
To: linux-bcache@vger.kernel.org
Cc: linux-block@vger.kernel.org, Coly Li <colyli@suse.de>
Subject: [PATCH 0/4] Fixes for potential deadlock during reboot
Date: Thu, 13 Jun 2019 00:19:54 +0800 [thread overview]
Message-ID: <20190612161958.2082-1-colyli@suse.de> (raw)
Hi folks,
Recently during my for-4.3 testing, I observe some lockdep warnings for
potential deadlock during reboot the kernel. Such potential deadlocks
are very hard to trigger in real life, but fix them and make lockdep
happy is still worthy IMHO.
This series is an effort to fix the potential deadlock issues, since
they are not critical stability fixes, they won't be CCed to stable
mailing list.
Thanks in advance for any commnet or review.
Coly Li
---
Coly Li (4):
bcache: avoid a deadlock in bcache_reboot()
bcache: acquire bch_register_lock later in cached_dev_detach_finish()
bcache: acquire bch_register_lock later in cached_dev_free()
bcache: fix potential deadlock in cached_def_free()
drivers/md/bcache/super.c | 49 +++++++++++++++++++++++++++++++++++++------
drivers/md/bcache/sysfs.c | 26 +++++++++++++++++++++++
drivers/md/bcache/writeback.c | 4 ++++
3 files changed, 73 insertions(+), 6 deletions(-)
--
2.16.4
next reply other threads:[~2019-06-12 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 16:19 Coly Li [this message]
2019-06-12 16:19 ` [PATCH 1/4] bcache: avoid a deadlock in bcache_reboot() Coly Li
2019-06-12 16:19 ` [PATCH 2/4] bcache: acquire bch_register_lock later in cached_dev_detach_finish() Coly Li
2019-06-12 16:19 ` [PATCH 3/4] bcache: acquire bch_register_lock later in cached_dev_free() Coly Li
2019-06-12 16:19 ` [PATCH 4/4] bcache: fix potential deadlock in cached_def_free() Coly Li
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=20190612161958.2082-1-colyli@suse.de \
--to=colyli@suse.de \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.