From: "Theodore Ts'o" <tytso@mit.edu>
To: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: fix fast commit alignment issues
Date: Wed, 2 Jun 2021 21:59:19 -0400 [thread overview]
Message-ID: <YLg3d/BxDgTaCPEm@mit.edu> (raw)
In-Reply-To: <20210519215920.2037527-1-harshads@google.com>
On Wed, May 19, 2021 at 02:59:20PM -0700, Harshad Shirwadkar wrote:
> From: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
>
> Fast commit recovery data on disk may not be aligned. So, when the
> recovery code reads it, this patch makes sure that fast commit info
> found on-disk is first memcpy-ed into an aligned variable before
> accessing it. As a consequence of it, we also remove some macros that
> could resulted in unaligned accesses.
>
> Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Applied, thanks.
- Ted
next prev parent reply other threads:[~2021-06-03 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 21:59 [PATCH] ext4: fix fast commit alignment issues Harshad Shirwadkar
2021-06-03 1:59 ` Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-11 21:24 Harshad Shirwadkar
2021-08-14 14:14 ` Theodore Ts'o
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=YLg3d/BxDgTaCPEm@mit.edu \
--to=tytso@mit.edu \
--cc=harshadshirwadkar@gmail.com \
--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).