Date: Tue, 19 Aug 2008 17:11:36 -0700 (PDT)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Bart Trojanowski <bart@jukie.net>
cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: vfat BKL/lock_super regression in v2.6.26-rc3-g8f59342
In-Reply-To: <20080820000339.GB28029@jukie.net>
Message-ID: <alpine.LFD.1.10.0808191709130.3324@nehalem.linux-foundation.org>
References: <20080819220311.GA28029@jukie.net> <alpine.LFD.1.10.0808191505590.3324@nehalem.linux-foundation.org> <20080820000339.GB28029@jukie.net>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 954
Lines: 23


On Tue, 19 Aug 2008, Bart Trojanowski wrote:
> 
> Ok, I will test your patch and let you know in a few minutes.

Btw, while you're at it, can you try doing some random writes to that 
thing, since the whole sync mount is quite possibly going to find a few 
other cases like this. 

IOW, _maybe_ you hit the only case that is ever going to be an issue for 
sync mounts, and maybe you didn't. In my eternal quest to never actually 
test anything myself, I'm hoping you can try some writing (and 
over-writing) of files, since writes to the filesystem is where the whole 
"sync" thing is going to show up (both metadata ie file creation and 
removal, and "real" data ie normal write/truncate calls).

			Linus
--
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/