All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ritesh Harjani <riteshh@linux.ibm.com>
To: linux-ext4@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
	Jan Kara <jack@suse.cz>,
	Harshad Shirwadkar <harshadshirwadkar@gmail.com>,
	Ritesh Harjani <riteshh@linux.ibm.com>
Subject: [RFC 0/6] ext4: fast_commit fixes and some minor cleanups
Date: Mon, 31 Jan 2022 20:46:49 +0530	[thread overview]
Message-ID: <cover.1643637037.git.riteshh@linux.ibm.com> (raw)

Hello,

Please find this small patch series which fixes one of the issue (causing data
abort exception) identified with fast_commit and flex_bg.

Although I have given -g quick, log group a run and didn't see any surprise
there. But a careful review in Patch-1 & Patch-6 will surely help! :)

Will shortly send out the fstest patch, which could trigger this.

Patch details
==============

Patch-1: Fixes a data abort which could happen during recovery with flex_bg
feature. This might be even needed to cc to stable, right?

Patch-[2-5]: Minor cleanups

Patch[6]: Good to have to avoid any accidental set/clear of critical FS Metadata

Ritesh Harjani (6):
  ext4: Fixes ext4_mb_mark_bb() with flex_bg with fast_commit
  ext4: Implement ext4_group_block_valid() as common function
  ext4: Use in_range() for range checking in ext4_fc_replay_check_excluded
  ext4: No need to test for block bitmap bits in ext4_mb_mark_bb()
  ext4: Refactor ext4_free_blocks() to pull out ext4_mb_clear_bb()
  ext4: Add extra check in ext4_mb_mark_bb() to prevent against possible corruption

 fs/ext4/block_validity.c |  31 ++++++
 fs/ext4/ext4.h           |   3 +
 fs/ext4/fast_commit.c    |   4 +-
 fs/ext4/mballoc.c        | 235 +++++++++++++++++++++++----------------
 4 files changed, 176 insertions(+), 97 deletions(-)

--
2.31.1


                 reply	other threads:[~2022-01-31 15:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cover.1643637037.git.riteshh@linux.ibm.com \
    --to=riteshh@linux.ibm.com \
    --cc=harshadshirwadkar@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.