linux-kernel - attempting to format brd device results in OOM kills

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1497803428.21567.4.camel@redhat.com>
Date:   Sun, 18 Jun 2017 12:30:28 -0400
From:   Jeff Layton <jlayton@...hat.com>
To:     Christoph Hellwig <hch@...radead.org>, Jens Axboe <axboe@...com>
Cc:     Hannes Reinecke <hare@...e.de>, LKML <linux-kernel@...r.kernel.org>
Subject: attempting to format brd device results in OOM kills

I've run across a regression from v4.11. If I boot a v4.12-rc1 or later
kernel, make a large brd device and try to format it, it quickly slows
down to a crawl and then the OOM killer kicks in.

I ran a bisect and it landed here:

commit f09a06a193d942a12c1a33c153388b3962222006 (HEAD, refs/bisect/bad)
Author: Christoph Hellwig <hch@....de>
Date:   Wed Apr 5 19:21:16 2017 +0200

    brd: remove discard support
    
    It's just a in-driver reimplementation of writing zeroes to the pages,
    which fails if the discards aren't page aligned.
    
    Signed-off-by: Christoph Hellwig <hch@....de>
    Reviewed-by: Hannes Reinecke <hare@...e.com>
    Signed-off-by: Jens Axboe <axboe@...com>


I've been reproducing it in a VM with ~8G allocated to it:

I have a modprobe.d file with this in it:

    options brd rd_nr=1 rd_size=1073741824

I then just:

    # modprobe brd
    # mkfs -t ext2 /dev/ram0

It keels over pretty quickly after that.

My .config is attached.

Cheers,
-- 
Jeff Layton <jlayton@...hat.com>
View attachment "config" of type "text/x-mpsub" (184999 bytes)