From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] mmp: fix 64-bit handling of s_mmp_block
Date: Tue, 3 Dec 2013 20:07:49 -0500 [thread overview]
Message-ID: <20131204010749.GA15658@thunk.org> (raw)
In-Reply-To: <1376085723-4314-1-git-send-email-adilger@dilger.ca>
On Fri, Aug 09, 2013 at 04:02:03PM -0600, Andreas Dilger wrote:
> Fix the checking of s_mmp_block in e2fsck_pass1() and
> ext2fs_mmp_read() to handle the high 32 bits of s_blocks_count.
> Remove redundant check of s_mmp_block in do_dump_mmp() right before
> ext2fs_mmp_read() is called.
>
> Also fix s_blocks_count_hi in check_backup_super_block(), since it
> cannot use the ext2fs_blocks_count() helper easily.
>
> Signed-off-by: Andreas Dilger <adilger@dilger.ca>
Applied, thanks. (Sorry for letting this fall through the cracks for
so long. Patchwork.ozlabs.org is my friend. :-)
- Ted
next prev parent reply other threads:[~2013-12-04 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 22:02 [PATCH] mmp: fix 64-bit handling of s_mmp_block Andreas Dilger
2013-12-04 1:07 ` Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-31 21:01 Andreas Dilger
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=20131204010749.GA15658@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@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).