linux-ext4 - Re: [PATCH 0/2] ext4: deadlocks after allocation failure in ext4_init_io

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]

Date:	Tue, 14 May 2013 15:06:28 +0800
From:	Zheng Liu <gnehzuil.liu@...il.com>
To:	Alexey Khoroshilov <khoroshilov@...ras.ru>, Jan Kara <jack@...e.cz>
Cc:	Theodore Ts'o <tytso@....edu>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
	spruce-project@...uxtesting.org
Subject: Re: [PATCH 0/2] ext4: deadlocks after allocation failure in
 ext4_init_io_end()

On Mon, May 13, 2013 at 11:08:11PM +0400, Alexey Khoroshilov wrote:
> Hi, Ted!
> 
> Our tests for ext4 with targeted fault injection were stalled in Uninterruptible Sleep State 
> when they simulate a memory allocation failure in ext4_init_io_end() while it is called from 
> mpage_da_submit_io() or ext4_writepage().
> 
> It looks like the problems are that pages left locked after failure handling.
> 
> I am not completely sure that my patches take into account all required aspects, 
> but the tests are passed if the patches are applied.
> 
> Please find below syslog excerpt for the first issue.
> 
> Found by Linux File System Verification project (linuxtesting.org/spruce). 

Hi Alexey,

Thanks for fixing this.  The patch series looks good to me.  But the
commit (ext4: use io_end for multiple bios) has been reverted in dev
branch of ext4 tree.  I forward the mail to Jan to let him know your
fixes.

Regards,
                                                - Zheng
--
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