From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH 1/2] ext4: grab write access inside ext4_file_dio_write Date: Wed, 20 Mar 2013 12:54:40 +0000 Message-ID: <20130320125440.GN21522@ZenIV.linux.org.uk> References: <1363783698-28092-1-git-send-email-dmonakhov@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, jack@suse.cz To: Dmitry Monakhov Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:38691 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934420Ab3CTMym (ORCPT ); Wed, 20 Mar 2013 08:54:42 -0400 Content-Disposition: inline In-Reply-To: <1363783698-28092-1-git-send-email-dmonakhov@openvz.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Mar 20, 2013 at 04:48:17PM +0400, Dmitry Monakhov wrote: > We are responsible hold write count before any fs-speciffic modifications > This patch should fix following warning: NAK. The right way to do it is to lift the damn thing out of ->aio_write() completely. See the last 3 commits in vfs.git#experimental...