linux-kernel - Bug?: unlink cause btrfs error but other fs don't

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]

Date:   Wed, 4 Sep 2019 16:02:24 +0800
From:   "Hongzhi, Song" <hongzhi.song@...driver.com>
To:     <linux-btrfs@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <josef@...icpanda.com>
Subject: Bug?: unlink cause btrfs error but other fs don't

Hi ,

*Kernel:*

     After v5.2-rc1, qemux86-64

     make -j40 ARCH=x86_64 CROSS_COMPILE=x86-64-gcc
     use qemu to bootup kernel

*Reproduce:*

     There is a test case failed on btrfs but success on other 
fs(ext4,ext3), see attachment.

     Download attachments:

         gcc test.c -o myout -Wall -lpthread

         copy myout and run.sh to your qemu same directory.

         on qemu:

             ./run.sh

     I found the block device size with btrfs set 512M will cause the error.
     256M and 1G all success.

*Error info:*

     "BTRFS warning (device loop0): could not allocate space for a 
delete; will truncate on mount"

*Related patch:*

     I use git bisect to find the following patch introduces the issue.

     commit c8eaeac7b734347c3afba7008b7af62f37b9c140
     Author: Josef Bacik <josef@...icpanda.com>
     Date:   Wed Apr 10 15:56:10 2019 -0400

         btrfs: reserve delalloc metadata differently
         ...

Anyone's reply will be appreciated.

--Hongzhi

Download attachment "run.sh" of type "application/x-shellscript" (604 bytes)

View attachment "test.c" of type "text/x-csrc" (3913 bytes)