From: Vyacheslav Dubeyko <slava@dubeyko.com>
To: Sergei Antonov <saproj@gmail.com>
Cc: Linux FS devel list <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
ChristophHellwig <hch@infradead.org>,
Hin-Tak Leung <htl10@users.sourceforge.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v3 01/15] hfsplus: add necessary declarations for journal replay
Date: Wed, 12 Feb 2014 20:38:32 +0400 [thread overview]
Message-ID: <1392223112.3104.14.camel@ubuntu> (raw)
In-Reply-To: <CABikg9xLex+0ufsS--TaSeo0C1zdwod7U-D4msnBGKLJ7DDLzA@mail.gmail.com>
On Wed, 2014-02-12 at 17:15 +0100, Sergei Antonov wrote:
> > The journal info block (struct hfsplus_journal_info_block) is big-endian
> > structure. The rest structures of HFS+ journal (struct hfsplus_journal_header,
> > struct hfsplus_blhdr, struct hfsplus_block_info) are little-endian.
>
> Journal header and block lists are either big-endian or little-endian.
> See JOURNAL_NEED_SWAP in Apple's code.
Do you know how to create journal with BE internal structures? Or have
you examples of journal with such structures? I haven't such examples.
And I can't see such opportunities in newfs_hfs tool. So, I don't think
that Journal header and block lists can be not little-endian. I can't
implement or test something unreal. Could you share the way of creation
HFS+ journal with big-endian Journal header and block lists?
Thanks,
Vyacheaslav Dubeyko.
next prev parent reply other threads:[~2014-02-12 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 14:25 [PATCH v3 01/15] hfsplus: add necessary declarations for journal replay Vyacheslav Dubeyko
2014-02-12 16:15 ` Sergei Antonov
2014-02-12 16:38 ` Vyacheslav Dubeyko [this message]
2014-02-12 16:50 ` Sergei Antonov
2014-02-12 17:59 ` Vyacheslav Dubeyko
2014-02-13 10:41 ` Sergei Antonov
2014-02-13 10:56 ` Vyacheslav Dubeyko
2014-02-13 20:07 ` Hin-Tak Leung
2014-02-14 7:22 ` Vyacheslav Dubeyko
2014-02-15 4:04 ` Hin-Tak Leung
2014-02-15 14:27 ` Vyacheslav Dubeyko
-- strict thread matches above, loose matches on Subject: below --
2014-02-15 16:12 Hin-Tak Leung
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=1392223112.3104.14.camel@ubuntu \
--to=slava@dubeyko.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=htl10@users.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=saproj@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).