On Tue, Nov 29, 2016 at 1:04 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
> 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.
Yeah, and to worsen things it's allocated and then destroyed on *every*
write. I'm in the process of re-writing that code for CONFIG_VMAP_STACK
and will look into fixing this as well.
In the meantime, disabling cephx message signing should take that
allocation out of the way.
Thanks,
Ilya
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
