From: Kent Overstreet <koverstreet@google.com>
To: linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org,
dm-devel@redhat.com
Cc: Kent Overstreet <koverstreet@google.com>, tj@kernel.org, axboe@kernel.dk
Subject: [PATCH 0/2] Avoid deadlocks with bio allocation
Date: Fri, 7 Sep 2012 15:12:51 -0700 [thread overview]
Message-ID: <1347055973-11581-1-git-send-email-koverstreet@google.com> (raw)
These patches were part of the block cleanups series I just sent out, but I
split them off. Nothing's changed with them lately, the last thing I added was
a bit of logic to the "punt to rescue" code to only punt bios that were
allocated from the current bio_set.
Kent Overstreet (2):
block: Reorder struct bio_set
block: Avoid deadlocks with bio allocation by stacking drivers
fs/bio.c | 87 +++++++++++++++++++++++++++++++++++++++++++++++++++--
include/linux/bio.h | 75 +++++++++++++++++++++++++--------------------
2 files changed, 126 insertions(+), 36 deletions(-)
--
1.7.12
next reply other threads:[~2012-09-07 22:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 22:12 Kent Overstreet [this message]
2012-09-07 22:12 ` [PATCH 1/2] block: Reorder struct bio_set Kent Overstreet
2012-09-07 22:12 ` [PATCH 2/2] block: Avoid deadlocks with bio allocation by stacking drivers Kent Overstreet
2012-09-08 19:36 ` Tejun Heo
2012-09-10 0:28 ` Kent Overstreet
2012-09-10 15:25 ` Vivek Goyal
2012-09-10 17:22 ` Tejun Heo
2012-09-10 20:24 ` Kent Overstreet
2012-09-10 20:40 ` Tejun Heo
2012-09-10 21:33 ` Kent Overstreet
2012-09-10 21:37 ` Tejun Heo
2012-09-10 21:56 ` Kent Overstreet
2012-09-10 22:09 ` Tejun Heo
2012-09-10 22:50 ` [dm-devel] " Alasdair G Kergon
2012-09-10 23:01 ` Tejun Heo
2012-09-10 23:06 ` Kent Overstreet
2012-09-10 23:09 ` Alasdair G Kergon
2012-09-10 23:35 ` Tejun Heo
2012-09-10 23:45 ` Alasdair G Kergon
2012-09-10 23:01 ` Kent Overstreet
2012-09-10 23:13 ` Tejun Heo
2012-09-11 18:36 ` Muthu Kumar
2012-09-11 18:45 ` Tejun Heo
2012-09-11 18:58 ` Muthu Kumar
2012-09-11 19:31 ` Kent Overstreet
2012-09-11 20:00 ` Muthu Kumar
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=1347055973-11581-1-git-send-email-koverstreet@google.com \
--to=koverstreet@google.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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
Powered by JetHome