linux-ext4 - RE: [PATCH v2 2/2] ext4: disable COLLAPSE

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

Date:	Mon, 21 Apr 2014 13:52:28 +0900
From:	Namjae Jeon <namjae.jeon@...sung.com>
To:	'Theodore Ts'o' <tytso@....edu>
Cc:	'linux-ext4' <linux-ext4@...r.kernel.org>,
	'Lukáš Czerner' <lczerner@...hat.com>
Subject: RE: [PATCH v2 2/2] ext4: disable COLLAPSE_RANGE for bigalloc

> On Sat, Apr 19, 2014 at 01:53:50PM +0900, Namjae Jeon wrote:
> > From: Namjae Jeon <namjae.jeon@...sung.com>
> >
> > Once COLLAPSE RANGE is be disable for ext4 with bigalloc feature till finding
> > root-cause of problem. It will be enable with fixing that regression of
> > xfstest(generic 075 and 091) again.
> >
> > Signed-off-by: Namjae Jeon <namjae.jeon@...sung.com>
> > Signed-off-by: Ashish Sangwan <a.sangwan@...sung.com>
> > Reviewed-by: Lukas Czerner <lczerner@...hat.com>
> 
> Thanks, applied.
> 
> What's the status of the "[2/3] ext4: fix ZERO_RANGE test failure in
> data journalling mode" patch.  Is it no longer needed?
It is needed. Currently, I am considering your suggestion of introducing
EXT4_I(inode)->i_write_mutex which can also include ext4_aio_mutex.

Thanks!
> 
>      		       	       	     - Ted

--
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