From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: [PATCH 1/1] locks: prevent side-effects of locks_release_private before file_lock is initialized Date: Tue, 26 Jun 2012 11:23:37 -0400 Message-ID: <20120626152336.GD14279@fieldses.org> References: <1339815965-1171-1-git-send-email-filbranden@gmail.com> <1339815965-1171-2-git-send-email-filbranden@gmail.com> <20120618200131.GA12351@fieldses.org> <20120626002908.GA14279@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Al Viro , Matthew Wilcox , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Filipe Brandenburger Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Jun 25, 2012 at 10:10:35PM -0400, Filipe Brandenburger wrote: > Just to let you know that I just tested the patch below on top of > 3.5.0-rc4 and it works fine... > > Do you like the idea of this second patch or do you prefer the > __locks_free_lock() one? Like I said: > Let's just go with your first patch and free the thing by hand (but > add a comment explaining why). > > Then come back and figure out how to make the interface clearer once > we've got the bug fixed. --b.