All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis Henriques (SUSE)" <luis.henriques@linux.dev>
To: Theodore Ts'o <tytso@mit.edu>, Andreas Dilger <adilger@dilger.ca>,
	Jan Kara <jack@suse.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Luis Henriques (SUSE)" <luis.henriques@linux.dev>
Subject: [RFC PATCH 0/2] ext4: two small fast commit fixes
Date: Tue, 21 May 2024 16:45:33 +0100	[thread overview]
Message-ID: <20240521154535.12911-1-luis.henriques@linux.dev> (raw)

Hi!

I've spent some time investigating an fstest failure when running it using
'-O fast_commit'.  As a result, I'm sending two patches that hopefully fix
this failure.  The first patch is the actual bug fix for the generic/047
fstest.  The second patch was just something I saw through code inspection.

Note that this generic/047 test also requires the fix I sent before[1], for
a different fstest failure.

[1] https://lore.kernel.org/all/20240515082857.32730-1-luis.henriques@linux.dev

Luis Henriques (SUSE) (2):
  ext4: fix fast commit inode enqueueing during a full journal commit
  jbd2: reset fast commit offset only after fs cleanup is done

 fs/ext4/fast_commit.c | 19 +++++++++++++------
 fs/jbd2/commit.c      |  2 +-
 2 files changed, 14 insertions(+), 7 deletions(-)


             reply	other threads:[~2024-05-21 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 15:45 Luis Henriques (SUSE) [this message]
2024-05-21 15:45 ` [RFC PATCH 1/2] ext4: fix fast commit inode enqueueing during a full journal commit Luis Henriques (SUSE)
2024-05-22 10:35   ` Jan Kara
2024-05-22 13:21     ` Luis Henriques
2024-05-21 15:45 ` [RFC PATCH 2/2] jbd2: reset fast commit offset only after fs cleanup is done Luis Henriques (SUSE)
2024-05-22 10:45   ` Jan Kara
2024-05-22 13:36     ` Luis Henriques
2024-05-23  7:44       ` Jan Kara
2024-05-23  8:52         ` Luis Henriques

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=20240521154535.12911-1-luis.henriques@linux.dev \
    --to=luis.henriques@linux.dev \
    --cc=adilger@dilger.ca \
    --cc=jack@suse.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@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.