linux-ext4 - Re: [PATCH] ext4: Add support for data=alloc_on

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: <49C275DB.2060906@redhat.com>
Date:	Thu, 19 Mar 2009 11:42:03 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	"Theodore Ts'o" <tytso@....edu>
CC:	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] ext4: Add support for data=alloc_on_commit mode

Eric Sandeen wrote:
> Theodore Ts'o wrote:
>> Add an ext3 bug-for-bug compatible analogue for data=ordered mode.  In
>> this mode, we force all delayed allocation blocks involved with the
>> to-be-commited transaction to be allocated, and then flushed out to
>> disk before the transaction is commited.
>>
>> Signed-off-by: "Theodore Ts'o" <tytso@....edu>
> 
> Haven't really looked into the cause yet but I was playing with this,
> and ran:
> 
> # rm -f bigfile smallfile; dd if=/dev/zero of=bigfile bs=1M count=8192;
> echo boo > smallfile; time /root/fsync smallfile; time /root/fsync bigfile
> 
> which resulted in:
> 
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000060
> IP: [<ffffffffa02a6de1>] alloc_on_commit_callback+0x27/0x7f [ext4]

This may have been user error ... ignore for now, I'll follow up if I
decide it's real.  :)

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html