From: Boaz Harrosh Subject: [PATCH 0/2] exofs: Double page_unlock BUG in write_begin/write_end Date: Fri, 08 Oct 2010 09:20:33 -0400 Message-ID: <4CAF1AA1.1090801@panasas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit To: linux-fsdevel , linux-kernel , open-osd , Benny Halevy Return-path: Received: from exprod5og112.obsmtp.com ([64.18.0.24]:39524 "HELO exprod5og112.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753673Ab0JHNWm (ORCPT ); Fri, 8 Oct 2010 09:22:42 -0400 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Testing at Bakeathon, I got a page_unlock BUG_ON triggered. I've found a very old bug, back from the days of the empire. It is time related and it only triggers since couple of rc-releases. The first patch is the bug fix and I'd want to push it to Linus for this version. If it's already to late I'll get it to the merge window with a CC for stable. The second patch is a cleanup that opened up do to the new variable introduced in the bugfix above. Which I'll push for the next release. [PATCH 1/2] exofs: Fix double page_unlock BUG in write_begin/end [PATCH 2/2] exofs: Cleaup read path in regard with read_for_write Thanks Boaz