From mboxrd@z Thu Jan 1 00:00:00 1970 From: Warren Turkal Subject: [PATCH 0/2] HFS+ journal improvement - take 5 Date: Wed, 19 Nov 2008 18:25:58 -0800 Message-ID: <1227147960-32355-1-git-send-email-wt@penguintechs.org> Cc: linux-fsdevel@vger.kernel.org, Warren Turkal To: Andrew Morton Return-path: Received: from wf-out-1314.google.com ([209.85.200.168]:59707 "EHLO wf-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751461AbYKTC0F (ORCPT ); Wed, 19 Nov 2008 21:26:05 -0500 Received: by wf-out-1314.google.com with SMTP id 27so247956wfd.4 for ; Wed, 19 Nov 2008 18:26:04 -0800 (PST) Sender: linux-fsdevel-owner@vger.kernel.org List-ID: This is a patchset to change the way that the HFS+ filesystem detects whether a volume has a journal or not. The code currently mounts an HFS+ volume read-only by default when a journal is detected. One can force a read/write mount by giving the "force" mount option. The current code has this behavior since there is no support for the HFS+ journal. My problem is that the detection of the journal could be better. The current code tests the attribute bit in the volume header that indicates there is a journal. If that bit is set, the code assumes that there is a journal. Unfortunately, this is not enough to really determine if there is a journal or not. When that bit is set, one must also examine the journal info block field of the volume header. If this field is 0, there is no journal, and the volume can be mounted read/write. Thanks, wt Warren Turkal (2): Identify journal info block in volume header. Fix journal detection on HFS+. fs/hfsplus/hfsplus_raw.h | 2 +- fs/hfsplus/super.c | 13 ++++++++++--- 2 files changed, 11 insertions(+), 4 deletions(-)