From: steve@chygwyn.com Subject: Re: [PATCH 5/10] gfs2: Fix error handling in write_super_lockfs/unlockfs Date: Fri, 26 Sep 2008 10:37:30 +0100 Message-ID: <20080926093730.GA5346@fogou.chygwyn.com> References: <20080926175821t-sato@mail.jp.nec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , Christoph Hellwig , "linux-fsdevel@vger.kernel.org" , "dm-devel@redhat.com" , "viro@ZenIV.linux.org.uk" , "linux-ext4@vger.kernel.org" , "xfs@oss.sgi.com" , "axboe@kernel.dk" , "mtk.manpages@googlemail.com" , "linux-kernel@vger.kernel.org" To: Takashi Sato Return-path: Received: from fogou.chygwyn.com ([195.171.2.24]:58690 "EHLO fogou.chygwyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751579AbYIZJjj (ORCPT ); Fri, 26 Sep 2008 05:39:39 -0400 Content-Disposition: inline In-Reply-To: <20080926175821t-sato@mail.jp.nec.com> Sender: linux-ext4-owner@vger.kernel.org List-ID: Hi, On Fri, Sep 26, 2008 at 05:58:21PM +0900, Takashi Sato wrote: > Changed write_super_lockfs so that it returns an error in case of an failure. > unlockfs always returns 0. Looks good now. Thanks, Steve.