Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753017AbbBQVLA (ORCPT ); Tue, 17 Feb 2015 16:11:00 -0500 Received: from mail-yk0-f178.google.com ([209.85.160.178]:49738 "EHLO mail-yk0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752617AbbBQVK7 (ORCPT ); Tue, 17 Feb 2015 16:10:59 -0500 Date: Tue, 17 Feb 2015 16:10:53 -0500 From: Jeff Layton To: Al Viro Cc: Linus Torvalds , linux-fsdevel , Linux Kernel Mailing List , "Kirill A. Shutemov" , "J. Bruce Fields" , Christoph Hellwig , Dave Chinner , Sasha Levin Subject: Re: [PATCH 0/4] locks: flock and lease related bugfixes, and remove i_flctx counters Message-ID: <20150217161053.2aa2b7d9@tlielax.poochiereds.net> In-Reply-To: <20150217202049.GN29656@ZenIV.linux.org.uk> References: <1424177190-14252-1-git-send-email-jeff.layton@primarydata.com> <20150217202049.GN29656@ZenIV.linux.org.uk> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1353 Lines: 43 On Tue, 17 Feb 2015 20:20:49 +0000 Al Viro wrote: > On Tue, Feb 17, 2015 at 11:55:01AM -0800, Linus Torvalds wrote: > > > Can we get that truncated series tested with some flock test suite? I > > assume there is *some* filesystem tester that tests some basic flock > > stuff, even if it clearly didn't catch the race due to the unlock in > > the middle.. > > LTP runltp -f syscalls does cover some of that; BTW, looks like fcntl11, > fcntl11_64, fcntl21 and fcntl21_64 in there got broken by something already > merged. Hadn't don bisect yet, but seeing > * NAME > * fcntl11.c > * > * DESCRIPTION > * Testcase to check locking of regions of a file > * > * ALGORITHM > * Test changing lock sections around a write lock > and > * NAME > * fcntl21.c > * > * DESCRIPTION > * Check locking of regions of a file > * > * ALGORITHM > * Test changing lock sections around a read lock > > I'd say that file locking merge is most likely suspect... Almost certainly. I'll take a look. Thanks, -- Jeff Layton -- 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/