From: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
To: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
Cc: kernel neophyte
<neophyte.hacker001-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Stefan Priebe <s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
Subject: Re: [PATCH] bcache: Fix a shrinker deadlock
Date: Fri, 30 Aug 2013 22:20:18 -0600 [thread overview]
Message-ID: <20130831042018.GP21481@kernel.dk> (raw)
In-Reply-To: <20130830211510.GA20307@kmo-pixel>
On Fri, Aug 30 2013, Kent Overstreet wrote:
> GFP_NOIO means we could be getting called recursively - mca_alloc() ->
> mca_data_alloc() - definitely can't use mutex_lock(bucket_lock) then.
> Whoops.
Kent, can you provide and updated repo with the pending patches? There's
been some churn here lately (and good fixes), would like to ensure I
don't miss anything.
--
Jens Axboe
next prev parent reply other threads:[~2013-08-31 4:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 0:29 Bcache sleeps forever on random writes kernel neophyte
[not found] ` <CAFkUHxd6xN3On4DTC7VnUgVuy8M57k=8eKYr47bKKnpQWS+p8A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-30 1:16 ` kernel neophyte
2013-08-30 21:15 ` [PATCH] bcache: Fix a shrinker deadlock Kent Overstreet
2013-08-31 4:20 ` Jens Axboe [this message]
2013-08-31 13:37 ` Stefan Priebe
2013-09-03 20:51 ` Stefan Priebe - Profihost AG
2013-09-04 23:35 ` kernel neophyte
2013-09-04 23:45 ` Kent Overstreet
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=20130831042018.GP21481@kernel.dk \
--to=axboe-tswwg44o7x1aa/9udqfwiw@public.gmane.org \
--cc=kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=neophyte.hacker001-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.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