From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH 2/2] xfs: V5 filesystem format support
Date: Sat, 30 May 2015 09:59:09 +0300 [thread overview]
Message-ID: <20150530095909.62c7b302@opensuse.site> (raw)
In-Reply-To: <1431502368-29422-3-git-send-email-jack@suse.cz>
В Wed, 13 May 2015 09:32:48 +0200
Jan Kara <jack@suse.cz> пишет:
>
> struct grub_xfs_sblock
> {
> @@ -54,12 +68,19 @@ struct grub_xfs_sblock
> grub_uint8_t log2_agblk;
> grub_uint8_t unused6[67];
> grub_uint8_t log2_dirblk;
> + grub_uint8_t unused7[7];
> + grub_uint32_t features2;
> + grub_uint8_t unused8[4];
> + grub_uint32_t sb_features_compat;
> + grub_uint32_t sb_features_ro_compat;
> + grub_uint32_t sb_features_incompat;
> + grub_uint32_t sb_features_log_incompat;
They do not seem to be really used. Normally the very first thing other
filesystems do is to check for incompatible features we do not support.
Even if there are no such such features right now you should add checks
to avoid attempt to access unsupported future format.
...
> @@ -281,6 +384,9 @@ grub_xfs_read_inode (struct grub_xfs_data *data, grub_uint64_t ino,
> grub_uint64_t block = grub_xfs_inode_block (data, ino);
> int offset = grub_xfs_inode_offset (data, ino);
>
> + grub_dprintf("xfs", "Reading inode (%llu) - %llu, %d\n",
PRIuGRUB_UINT64_T and drop casts.
> + (unsigned long long) ino,
> + (unsigned long long) block, offset);
next prev parent reply other threads:[~2015-05-30 6:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 7:32 [PATCH 0/2 v2] Support for XFS v5 filesystem Jan Kara
2015-05-13 7:32 ` [PATCH 1/2] xfs: Add helpers for inode size Jan Kara
2015-05-30 7:00 ` Andrei Borzenkov
2015-06-01 12:22 ` Jan Kara
2015-05-13 7:32 ` [PATCH 2/2] xfs: V5 filesystem format support Jan Kara
2015-05-30 6:59 ` Andrei Borzenkov [this message]
2015-06-01 12:20 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2015-06-01 12:28 [PATCH 0/2 v3] Support for XFS v5 filesystem Jan Kara
2015-06-01 12:28 ` [PATCH 2/2] xfs: V5 filesystem format support Jan Kara
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=20150530095909.62c7b302@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=jack@suse.cz \
/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).