[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fc27dc51-65a7-f2fa-6b29-01a1d5eaec6c@maciej.szmigiero.name>
Date: Wed, 23 Dec 2020 22:19:41 +0100
From: "Maciej S. Szmigiero" <mail@...iej.szmigiero.name>
To: Ignat Korchagin <ignat@...udflare.com>
Cc: Alasdair G Kergon <agk@...hat.com>,
Mike Snitzer <snitzer@...hat.com>,
device-mapper development <dm-devel@...hat.com>,
dm-crypt@...ut.de, linux-kernel <linux-kernel@...r.kernel.org>,
Eric Biggers <ebiggers@...nel.org>,
Damien Le Moal <Damien.LeMoal@....com>,
Mikulas Patocka <mpatocka@...hat.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
kernel-team <kernel-team@...udflare.com>,
Nobuto Murata <nobuto.murata@...onical.com>,
Chris Mason <clm@...com>, Josef Bacik <josef@...icpanda.com>,
David Sterba <dsterba@...e.com>, linux-btrfs@...r.kernel.org,
linux-crypto <linux-crypto@...r.kernel.org>
Subject: Re: dm-crypt with no_read_workqueue and no_write_workqueue + btrfs
scrub = BUG()
On 23.12.2020 22:09, Ignat Korchagin wrote:
(..)
> I've been looking into this for the last couple of days because of
> other reports [1].
> Just finished testing a possible solution. Will submit soon.
Thanks for looking into it.
By the way, on a bare metal I am actually hitting a different problem
(scheduling while atomic) when scrubbing a btrfs filesystem, just as one
of your users from that GitHub report had [1].
I've pasted that backtrace in my original Dec 14 message.
Thanks,
Maciej
[1]: https://github.com/cloudflare/linux/issues/1#issuecomment-736734243
Powered by blists - more mailing lists