From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergei Antonov Subject: Re: [PATCH] hfsplus: release bnode pages after use, not before Date: Thu, 18 Jun 2015 15:09:07 +0200 Message-ID: References: <1433637776-3559-1-git-send-email-saproj@gmail.com> <1433778309.2513.11.camel@ubuntu-slavad-14.04> <1433781918.2659.3.camel@slavad-ubuntu-14.04> <20150609151545.8a146bb5d29051e604d4d211@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Andrew Morton , Viacheslav Dubeyko , Anton Altaparmakov , "linux-fsdevel@vger.kernel.org" , Sasha Levin , Al Viro , Christoph Hellwig , Hin-Tak Leung , Sougata Santra To: Hin-Tak Leung Return-path: Received: from mail-ob0-f171.google.com ([209.85.214.171]:33440 "EHLO mail-ob0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755633AbbFRNJI (ORCPT ); Thu, 18 Jun 2015 09:09:08 -0400 Received: by obbkn5 with SMTP id kn5so25015256obb.0 for ; Thu, 18 Jun 2015 06:09:07 -0700 (PDT) In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 18 June 2015 at 01:26, Hin-Tak Leung wrote: > On 14 June 2015 at 15:18, Sergei Antonov wrote: >> On 14 June 2015 at 04:27, Hin-Tak Leung wrote: >>> On 10 June 2015 at 00:40, Sergei Antonov wrote: >>> ... >>>> I did not try to change the logic of the driver. Just fixed one >>>> glaring defect. Which, by the way, in addition to the aforementioned >>>> bug by Sasha Levin caused: >>>> 1. A "du"-related bug reported by Hin-Tak Leung earlier in the list. >>>> 2. https://bugzilla.kernel.org/show_bug.cgi?id=63841 >>>> 3. https://bugzilla.kernel.org/show_bug.cgi?id=78761 >>>> 4. https://bugzilla.kernel.org/show_bug.cgi?id=42342 >>> >>> For some unknown reason majordomo won't let my regular sourceforge >>> account/alias post >>> to its lists (not just fsdevel, but also git), anyway, I just managed >>> to reproduced the issue - >> >> With the patch or without? > > Without. My older computer died about 9 months ago and I have not tried > to see the problem on my current hardware until now. The point > I am trying to see is to first see the problem on my current hardware, > then test the change (which I'll hope to find time to do in the next few days). > Otherwise, it is from not-see-problem to not-see-problem. > > I'll write again after I've tested the change. I'm looking forward to it. The result of the test (which I'm sure will show the bug is gone) will be by far more valuable contribution than your other messages in the thread.