linux-ext4 - Re: [PATCH 1/2] ext4: Do not allow retry alloc loop under open transaction

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: <87wrytqlji.fsf@linux.vnet.ibm.com>
Date:	Thu, 04 Feb 2010 17:07:21 +0530
From:	"Aneesh Kumar K. V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	Dmitry Monakhov <dmonakhov@...nvz.org>, linux-ext4@...r.kernel.org
Cc:	tytso@....edu
Subject: Re: [PATCH 1/2] ext4: Do not allow retry alloc loop under open
 transaction

On Wed, 03 Feb 2010 21:27:31 +0300, Dmitry Monakhov <dmonakhov@...nvz.org> wrote:
> 
> Some times we call ->write_begin() with opened journal
> but write_begin() may internally call ext4_should_retry_alloc()
> in case of ENOSPC, which result in deadlock.
> This patch introduce new AOP_FLAG which should be tested on retry
> alloc path.
> 

Can you explain this further. We do a journal_stop before
ext4_should_retry_alloc. So not sure about the deadlock.

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