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 1/2] Identify journal info block in volume header.
Date: Wed, 19 Nov 2008 18:25:59 -0800 [thread overview]
Message-ID: <1227147960-32355-2-git-send-email-wt@penguintechs.org> (raw)
In-Reply-To: <1227147960-32355-1-git-send-email-wt@penguintechs.org>
The HFS+ support in the kernel currently will mount an HFS+ volume read-only if
the volume header has the attribute bit set that indicates there is a journal.
The kernel does this because there is no support for a journalled HFS+ volume.
The problem is that this is only half of what needs to be checked to see if
there really is a journal. There is also an entry in the volume header that
tells you where to find the journal info block. In the kernel version of the
kernel, this 4 byte block is labeled reserved. This patch identifies the journal
info block in the header.
Signed-off-by: Warren Turkal <wt@penguintechs.org>
---
fs/hfsplus/hfsplus_raw.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/hfsplus/hfsplus_raw.h b/fs/hfsplus/hfsplus_raw.h
index fe99fe8..14f1dd8 100644
--- a/fs/hfsplus/hfsplus_raw.h
+++ b/fs/hfsplus/hfsplus_raw.h
@@ -94,7 +94,7 @@ struct hfsplus_vh {
__be16 version;
__be32 attributes;
__be32 last_mount_vers;
- u32 reserved;
+ __be32 journal_info_block;
__be32 create_date;
__be32 modify_date;
--
1.5.6.3
next prev parent reply other threads:[~2008-11-20 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 2:25 [PATCH 0/2] HFS+ journal improvement - take 5 Warren Turkal
2008-11-20 2:25 ` Warren Turkal [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 4:01 [PATCH 0/2] HFS+ journal improvement - take 6 Warren Turkal
2008-11-21 4:01 ` [PATCH 1/2] Identify journal info block in volume header 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-2-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.