linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Warren Turkal <wt@penguintechs.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, Warren Turkal <wt@penguintechs.org>
Subject: [PATCH 0/2] HFS+ journal improvement - take 5
Date: Wed, 19 Nov 2008 18:25:58 -0800	[thread overview]
Message-ID: <1227147960-32355-1-git-send-email-wt@penguintechs.org> (raw)

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(-)


             reply	other threads:[~2008-11-20  2:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20  2:25 Warren Turkal [this message]
2008-11-20  2:25 ` [PATCH 1/2] Identify journal info block in volume header Warren Turkal
2008-11-20  2:26   ` [PATCH 2/2] Fix journal detection on HFS+ Warren Turkal
2008-11-20 11:29     ` Jörn Engel
2008-11-20 17:02       ` Warren Turkal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1227147960-32355-1-git-send-email-wt@penguintechs.org \
    --to=wt@penguintechs.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).