lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 23 Dec 2020 21:31:29 +0000
From:   Ignat Korchagin <>
To:     "Maciej S. Szmigiero" <>
Cc:     Alasdair G Kergon <>,
        Mike Snitzer <>,
        device-mapper development <>,, linux-kernel <>,
        Eric Biggers <>,
        Damien Le Moal <>,
        Mikulas Patocka <>,
        Herbert Xu <>,
        kernel-team <>,
        Nobuto Murata <>,
        Chris Mason <>, Josef Bacik <>,
        David Sterba <>,,
        linux-crypto <>
Subject: Re: dm-crypt with no_read_workqueue and no_write_workqueue + btrfs
 scrub = BUG()

On Wed, Dec 23, 2020 at 9:20 PM Maciej S. Szmigiero
<> wrote:
> 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].

That is because dm-crypt calls "wait_for_completion" in rare cases
when Crypto API (cryptd) backlogs the decryption request. I've
reproduced that one as well (even with no FS).
We never hit these problems in the original testing probably due to
the fact we mostly used xtsproxy custom crypto module, which is
totally synchronous.
I did test it later with standard crypto, but did not encounter these
problems as well most likely because it is also depends which storage
driver underneath we are using: most of them do not submit read
requests to dm-crypt in irq/softirq context in the first place

> I've pasted that backtrace in my original Dec 14 message.
> Thanks,
> Maciej
> [1]:


Powered by blists - more mailing lists