From: Jan Kara <jack@suse.cz>
To: "Luis Henriques (SUSE)" <luis.henriques@linux.dev>
Cc: Theodore Ts'o <tytso@mit.edu>, Andreas Dilger <adilger@dilger.ca>,
Jan Kara <jack@suse.cz>,
Harshad Shirwadkar <harshadshirwadkar@gmail.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] ext4: fix incorrect tid assumption in __jbd2_log_wait_for_space()
Date: Wed, 24 Jul 2024 11:20:04 +0200 [thread overview]
Message-ID: <20240724092004.mzwdecz35cal227n@quack3> (raw)
In-Reply-To: <20240723154402.21125-3-luis.henriques@linux.dev>
On Tue 23-07-24 16:44:00, Luis Henriques (SUSE) wrote:
> Function __jbd2_log_wait_for_space() assumes that '0' is not a valid value
> for transaction IDs, which is incorrect. Don't assume that and invoke
> jbd2_log_wait_commit() if the journal had a committing transaction instead.
>
> Signed-off-by: Luis Henriques (SUSE) <luis.henriques@linux.dev>
Looks good. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/jbd2/checkpoint.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/fs/jbd2/checkpoint.c b/fs/jbd2/checkpoint.c
> index 951f78634adf..77bc522e6821 100644
> --- a/fs/jbd2/checkpoint.c
> +++ b/fs/jbd2/checkpoint.c
> @@ -79,9 +79,12 @@ __releases(&journal->j_state_lock)
> if (space_left < nblocks) {
> int chkpt = journal->j_checkpoint_transactions != NULL;
> tid_t tid = 0;
> + bool has_transaction = false;
>
> - if (journal->j_committing_transaction)
> + if (journal->j_committing_transaction) {
> tid = journal->j_committing_transaction->t_tid;
> + has_transaction = true;
> + }
> spin_unlock(&journal->j_list_lock);
> write_unlock(&journal->j_state_lock);
> if (chkpt) {
> @@ -89,7 +92,7 @@ __releases(&journal->j_state_lock)
> } else if (jbd2_cleanup_journal_tail(journal) == 0) {
> /* We were able to recover space; yay! */
> ;
> - } else if (tid) {
> + } else if (has_transaction) {
> /*
> * jbd2_journal_commit_transaction() may want
> * to take the checkpoint_mutex if JBD2_FLUSHED
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-07-24 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 15:43 [PATCH 0/4] ext4: fix incorrect tid assumptions Luis Henriques (SUSE)
2024-07-23 15:43 ` [PATCH 1/4] ext4: fix incorrect tid assumption in ext4_wait_for_tail_page_commit() Luis Henriques (SUSE)
2024-07-24 9:17 ` Jan Kara
2024-07-24 13:35 ` Luis Henriques
2024-07-23 15:44 ` [PATCH 2/4] ext4: fix incorrect tid assumption in __jbd2_log_wait_for_space() Luis Henriques (SUSE)
2024-07-24 9:20 ` Jan Kara [this message]
2024-07-23 15:44 ` [PATCH 3/4] ext4: fix incorrect tid assumption in jbd2_journal_shrink_checkpoint_list() Luis Henriques (SUSE)
2024-07-24 9:29 ` Jan Kara
2024-07-24 13:38 ` Luis Henriques
2024-07-23 15:44 ` [PATCH 4/4] ext4: fix incorrect tid assumption in ext4_fc_mark_ineligible() Luis Henriques (SUSE)
2024-07-24 10:15 ` Jan Kara
2024-07-24 14:02 ` Luis Henriques
2024-07-24 15:13 ` 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=20240724092004.mzwdecz35cal227n@quack3 \
--to=jack@suse.cz \
--cc=adilger@dilger.ca \
--cc=harshadshirwadkar@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@linux.dev \
--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 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).