Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762874AbWLKM2B (ORCPT ); Mon, 11 Dec 2006 07:28:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762873AbWLKM2B (ORCPT ); Mon, 11 Dec 2006 07:28:01 -0500 Received: from mailhub.sw.ru ([195.214.233.200]:27024 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762874AbWLKM2B (ORCPT ); Mon, 11 Dec 2006 07:28:01 -0500 Message-ID: <457D512F.3020605@sw.ru> Date: Mon, 11 Dec 2006 15:38:07 +0300 From: Kirill Korotaev User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060417 X-Accept-Language: en-us, en, ru MIME-Version: 1.0 To: Andrew Morton CC: linux-kernel@vger.kernel.org, Linux Memory Management , devel@openvz.org, Monakhov Dmintiy Subject: Re: [Devel] [PATCH] incorrect error handling inside generic_file_direct_write References: <87k60y1rq4.fsf@sw.ru> In-Reply-To: <87k60y1rq4.fsf@sw.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2443 Lines: 71 I guess you forgot to add Andrew on CC. Thanks, Kirill > OpenVZ team has discovered error inside generic_file_direct_write() > If generic_file_direct_IO() has fail (ENOSPC condition) it may have instantiated > a few blocks outside i_size. And fsck will complain about wrong i_size > (ext2, ext3 and reiserfs interpret i_size and biggest block difference as error), > after fsck will fix error i_size will be increased to the biggest block, > but this blocks contain gurbage from previous write attempt, this is not > information leak, but its silence file data corruption. > We need truncate any block beyond i_size after write have failed , do in simular > generic_file_buffered_write() error path. > > Exampe: > open("mnt2/FILE3", O_WRONLY|O_CREAT|O_DIRECT, 0666) = 3 > write(3, "aaaaaa"..., 4096) = -1 ENOSPC (No space left on device) > > stat mnt2/FILE3 > File: `mnt2/FILE3' > Size: 0 Blocks: 4 IO Block: 4096 regular empty file > >>>>>>>>>>>>>>>>>>>>>>>^^^^^^^^^^ file size is less than biggest block idx > > Device: 700h/1792d Inode: 14 Links: 1 > Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) > > fsck.ext2 -f -n mnt1/fs_img > Pass 1: Checking inodes, blocks, and sizes > Inode 14, i_size is 0, should be 2048. Fix? no > > Signed-off-by: Dmitriy Monakhov > ---------- > > > ------------------------------------------------------------------------ > > diff --git a/mm/filemap.c b/mm/filemap.c > index 7b84dc8..bf7cf6c 100644 > --- a/mm/filemap.c > +++ b/mm/filemap.c > @@ -2041,6 +2041,14 @@ generic_file_direct_write(struct kiocb * > mark_inode_dirty(inode); > } > *ppos = end; > + } else if (written < 0) { > + loff_t isize = i_size_read(inode); > + /* > + * generic_file_direct_IO() may have instantiated a few blocks > + * outside i_size. Trim these off again. > + */ > + if (pos + count > isize) > + vmtruncate(inode, isize); > } > > /* > > > ------------------------------------------------------------------------ > > _______________________________________________ > Devel mailing list > Devel@openvz.org > https://openvz.org/mailman/listinfo/devel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/