From: Luis Henriques <luis.henriques@linux.dev>
To: Jan Kara <jack@suse.cz>
Cc: Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger@dilger.ca>,
Harshad Shirwadkar <harshadshirwadkar@gmail.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] ext4: fix incorrect tid assumption in ext4_wait_for_tail_page_commit()
Date: Wed, 24 Jul 2024 14:35:44 +0100 [thread overview]
Message-ID: <874j8elxov.fsf@linux.dev> (raw)
In-Reply-To: <20240724091713.e4w2hskcybulz27z@quack3> (Jan Kara's message of "Wed, 24 Jul 2024 11:17:13 +0200")
On Wed, Jul 24 2024, Jan Kara wrote:
> On Tue 23-07-24 16:43:59, Luis Henriques (SUSE) wrote:
>> Function ext4_wait_for_tail_page_commit() 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>
>> ---
>> fs/ext4/inode.c | 10 ++++++----
>> 1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
>> index 941c1c0d5c6e..e65fc2086701 100644
>> --- a/fs/ext4/inode.c
>> +++ b/fs/ext4/inode.c
>> @@ -5279,8 +5279,9 @@ static void ext4_wait_for_tail_page_commit(struct inode *inode)
>> {
>> unsigned offset;
>> journal_t *journal = EXT4_SB(inode->i_sb)->s_journal;
>> - tid_t commit_tid = 0;
>> + tid_t commit_tid;
>> int ret;
>> + bool has_transaction = false;
>>
>> offset = inode->i_size & (PAGE_SIZE - 1);
>> /*
>> @@ -5305,12 +5306,13 @@ static void ext4_wait_for_tail_page_commit(struct inode *inode)
>> folio_put(folio);
>> if (ret != -EBUSY)
>> return;
>> - commit_tid = 0;
>
> We should set "has_transaction = false" here to make things work properly
> when looping... Otherwise looks good.
Ah! Good point. I'll fix that, thanks!
Cheers,
--
Luís
>
> Honza
>
>> read_lock(&journal->j_state_lock);
>> - if (journal->j_committing_transaction)
>> + if (journal->j_committing_transaction) {
>> commit_tid = journal->j_committing_transaction->t_tid;
>> + has_transaction = true;
>> + }
>> read_unlock(&journal->j_state_lock);
>> - if (commit_tid)
>> + if (has_transaction)
>> jbd2_log_wait_commit(journal, commit_tid);
>> }
>> }
>>
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
next prev parent reply other threads:[~2024-07-24 13:35 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 [this message]
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
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=874j8elxov.fsf@linux.dev \
--to=luis.henriques@linux.dev \
--cc=adilger@dilger.ca \
--cc=harshadshirwadkar@gmail.com \
--cc=jack@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox