From: Christoph Hellwig <hch@infradead.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: ceph-devel@vger.kernel.org, linux-xfs@vger.kernel.org,
"Michael Olbrich" <m.olbrich@pengutronix.de>,
"Björn Lässig" <b.laessig@pengutronix.de>
Subject: Re: XFS on RBD deadlock
Date: Tue, 29 Nov 2016 04:04:05 -0800 [thread overview]
Message-ID: <20161129120405.GA11089@infradead.org> (raw)
In-Reply-To: <1480418228.2258.28.camel@pengutronix.de>
On Tue, Nov 29, 2016 at 12:17:08PM +0100, Lucas Stach wrote:
> 2. RBD worker is trying to handle the XFS block request, but the
> involved crypto code recurses into the XFS superblock shrinker, as it's
> trying to allocate memory with GFP_KERNEL in __crypto_alloc_tfm.
And that's where the issues start - crypto_alloc_skcipher and friends
are not intended to be called from the writeback path.
next prev parent reply other threads:[~2016-11-29 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 11:17 XFS on RBD deadlock Lucas Stach
2016-11-29 12:04 ` Christoph Hellwig [this message]
2016-11-29 13:19 ` Ilya Dryomov
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=20161129120405.GA11089@infradead.org \
--to=hch@infradead.org \
--cc=b.laessig@pengutronix.de \
--cc=ceph-devel@vger.kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-xfs@vger.kernel.org \
--cc=m.olbrich@pengutronix.de \
/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).