linux-kernel - Re: [PATCH 1/1] btrfs: btrfs_calc_avail_data_space cope with no read/write devices V2

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4ED434A9.8020809@cn.fujitsu.com>
Date:	Tue, 29 Nov 2011 09:26:01 +0800
From:	Li Zefan <lizf@...fujitsu.com>
To:	Andy Whitcroft <apw@...onical.com>
CC:	Jonathan Nieder <jrnieder@...il.com>,
	Chris Mason <chris.mason@...cle.com>,
	Josef Bacik <josef@...hat.com>,
	Miao Xie <miaox@...fujitsu.com>,
	Ivan Vilata i Balaguer <ivan@...idor.net>,
	linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] btrfs: btrfs_calc_avail_data_space cope with no read/write
 devices V2

Andy Whitcroft wrote:
> On Mon, Nov 28, 2011 at 06:11:06AM -0600, Jonathan Nieder wrote:
>> Hi,
>>
>> Andy Whitcroft wrote:
>>
>>> When we mount a btrfs filesystem from read-only media there will be no
>>> read/write devices; for example mounting an SD card with its lock enabled.
>>> This triggers an immediate BUG during mount:
>>>
>>>   kernel BUG at .../fs/btrfs/super.c:984!
>> [...]
>>> BugLink: http://bugs.launchpad.net/bugs/816770
>>> Signed-off-by: Andy Whitcroft <apw@...onical.com>
>>> ---
>>
>> Fixes http://bugs.debian.org/649847
>> Tested-by: Ivan Vilata i Balaguer <ivan@...idor.net>
>>
>> This patch fixes a regression introduced by 6d07bcec969a ("btrfs: fix
>> wrong free space information of btrfs"), which hit mainline in
>> v2.6.38-rc1.  Josef Bacik acked the patch, but I can't seem to find it
>> in linux-next, linux-btrfs, or Josef's btrfs-work tree.  Maybe it was
>> just forgotten.
>>
>> What can I do to help this patch get unstuck?
> 
> I had completely forgotten about this one.  I wonder where it did get
> to.  I seem to remember testing this in house successfully.
> 

This patch has the same problem with your previous one, that it will set
f_bavail to 0. I've sent out a new patch yesterday.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/