linux-ext4 - Re: [PATCH 2/3] jbd2 : Fix journal start by passing a parameter to specify if the caller can deal with ENOMEM

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: <4DDCB3FA.2070009@gmail.com>
Date:	Wed, 25 May 2011 00:47:06 -0700
From:	Manish Katiyar <mkatiyar@...il.com>
To:	Jan Kara <jack@...e.cz>
CC:	tytso@....edu, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 2/3] jbd2 : Fix journal start by passing a parameter to
 specify if the caller can deal with ENOMEM

On 05/25/2011 12:44 AM, Jan Kara wrote:
> This patch is OK as such but as I wrote in a reply to a later patch in
> the series, you also need to pass 'errok' to start_this_handle() instead of
> gfp_mask as well. Then in start_this_handle() you can use 'errok' to decide
> whether we should retry the allocation or not instead of gfp_mask. And just
> call kzalloc in start_this_handle() with GFP_NOFS... Thanks.

Hi Jan,

   ok.. I will do it as a separate patch.

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