From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Ts'o Subject: Re: [git pull] vfs pile 1 Date: Wed, 11 Jan 2012 10:23:37 -0500 Message-ID: <20120111152337.GA4589@thunk.org> References: <20120105022318.GG23916@ZenIV.linux.org.uk> <20120111115846.GA2646@infradead.org> <1326285382.13736.4.camel@tucsk.pomaz.szeredi.hu> <20120111124001.GA834@infradead.org> <1326287556.13736.12.camel@tucsk.pomaz.szeredi.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , Linus Torvalds , Al Viro , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Toshiyuki Okajima To: Miklos Szeredi Return-path: Content-Disposition: inline In-Reply-To: <1326287556.13736.12.camel@tucsk.pomaz.szeredi.hu> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Jan 11, 2012 at 02:12:36PM +0100, Miklos Szeredi wrote: > > Yes. a) really isn't an option - we don't want to spew thousands of > > useless messages during a log recovery for an operation that's totally > > normal. b) is okay, too - but it's not just xfs that needs to be > > covered, but any fs that support the concept of recovering from open > > but unlinked inodes after a crash. It's just that no one else seems > > to have regular QA for that code path. > > Since it's a ratelimited printk there won't be thousands of messages. I > think this is just a cosmetic issue and lack of QA isn't a problem. If > the messages are bothersome it can be fixed. We're going to spew messages in ext3/4 for orphan inodes as well (thanks for Cristoph for pointing that out). I can put in a similar kludge, but maybe there should be a _set_nlink() that skips the check? We do our own more sophisticated check in and will do appropriate error handling in ext4_iget() anyway, so it's just a waste in that particular codepath anyway. - Ted