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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <853d3a5e-6e65-a7d8-df52-e293cad17600@windriver.com>
Date:   Thu, 5 Sep 2019 09:36:31 +0800
From:   "Hongzhi, Song" <hongzhi.song@...driver.com>
To:     Josef Bacik <josef@...icpanda.com>
CC:     <linux-btrfs@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: Bug?: unlink cause btrfs error but other fs don't


On 9/4/19 6:48 PM, Josef Bacik wrote:
> On Wed, Sep 04, 2019 at 04:02:24PM +0800, Hongzhi, Song wrote:
>> 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
>>          ...
>>
>>
> I meant to reply to this but couldn't find the original thread.  The patches I
> wrote for this merge window were to address this issue.  Thanks,
>
> Josef


Ok, thank your, I will try to search them.

--Hongzhi


>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ