Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758211AbXEJTbA (ORCPT ); Thu, 10 May 2007 15:31:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754307AbXEJTax (ORCPT ); Thu, 10 May 2007 15:30:53 -0400 Received: from mail.fieldses.org ([66.93.2.214]:35473 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753656AbXEJTax (ORCPT ); Thu, 10 May 2007 15:30:53 -0400 Date: Thu, 10 May 2007 15:30:50 -0400 To: Doug Chapman Cc: linux-kernel@vger.kernel.org, hch@infradead.org, Marc Eshel Subject: Re: post 2.6.21 regression in F_GETLK Message-ID: <20070510193050.GQ13719@fieldses.org> References: <1178823375.7247.11.camel@dchapman.boston.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1178823375.7247.11.camel@dchapman.boston.redhat.com> User-Agent: Mutt/1.5.13 (2006-08-11) From: "J. Bruce Fields" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 815 Lines: 22 On Thu, May 10, 2007 at 02:56:15PM -0400, Doug Chapman wrote: > A recent regression (introduced after 2.6.21) was caught by the LTP test > fcntl11. It appears that F_GETLK is not properly checking for existing > F_RDLCK and allows taking out a write lock. Ouch. > This can be demonstrated by either running fcntl11 from the LTP suite or > I have hacked up a much shorter version which demonstrates the issue and > am attaching it. > > Using git bisect I came up with this commit as the one that introduced > the issue. Thanks for the report--investigating.... --b. - 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/