linux-ext4 - Re: A question about EXT4_INODE_JOURNAL

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, 12 Aug 2015 06:07:08 +0000 (GMT)
From:	Daeho Jeong <daeho.jeong@...sung.com>
To:	Theodore Ts'o <tytso@....edu>
Cc:	정대호 <daeho.jeong@...sung.com>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	"daehojng@...il.com" <daehojng@...il.com>
Subject: Re: A question about EXT4_INODE_JOURNAL_DATA flag with delalloc

Ted, thanks for your response.

I just have tested the below test by temporally enabling per-file data journalling with delalloc
and it didn't cause kernel oops any more. I will check further whether per-file data journalling
while allowing the rest of the file system to be using delalloc will cause another type of problem
or not.

 dd if=/dev/zero of=/mnt/test1/file bs=1M count=4
 chattr +j /mnt/test1/file
 dd if=/dev/zero of=/mnt/test1/file bs=1M count=4 conv=notrunc
 chattr -j /mnt/test1/file

Best Regards,