From: Jan Kara <jack@suse.cz>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.com>
Subject: Re: [PATCH] jbd2: make sure jh have b_transaction set in refile/unlink_buffer
Date: Wed, 17 Jun 2020 14:15:00 +0200 [thread overview]
Message-ID: <20200617121500.GA29763@quack2.suse.cz> (raw)
In-Reply-To: <20200617091031.6558-1-lczerner@redhat.com>
On Wed 17-06-20 11:10:31, Lukas Czerner wrote:
> Callers of __jbd2_journal_unfile_buffer() and
> __jbd2_journal_refile_buffer() assume that the b_transaction is set. In
> fact if it's not, we can end up with journal_head refcounting errors
> leading to crash much later that might be very hard to track down. Add
> asserts to make sure that is the case.
>
> We also make sure that b_next_transaction is NULL in
> __jbd2_journal_unfile_buffer() since the callers expect that as well and
> we should not get into that stage in this state anyway, leading to
> problems later on if we do.
>
> Tested with fstests.
>
> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Thanks! The patch looks good to me. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/jbd2/transaction.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/fs/jbd2/transaction.c b/fs/jbd2/transaction.c
> index e91aad3637a2..e65e0aca2826 100644
> --- a/fs/jbd2/transaction.c
> +++ b/fs/jbd2/transaction.c
> @@ -2026,6 +2026,9 @@ static void __jbd2_journal_temp_unlink_buffer(struct journal_head *jh)
> */
> static void __jbd2_journal_unfile_buffer(struct journal_head *jh)
> {
> + J_ASSERT_JH(jh, jh->b_transaction != NULL);
> + J_ASSERT_JH(jh, jh->b_next_transaction == NULL);
> +
> __jbd2_journal_temp_unlink_buffer(jh);
> jh->b_transaction = NULL;
> }
> @@ -2572,6 +2575,13 @@ bool __jbd2_journal_refile_buffer(struct journal_head *jh)
>
> was_dirty = test_clear_buffer_jbddirty(bh);
> __jbd2_journal_temp_unlink_buffer(jh);
> +
> + /*
> + * b_transaction must be set, otherwise the new b_transaction won't
> + * be holding jh reference
> + */
> + J_ASSERT_JH(jh, jh->b_transaction != NULL);
> +
> /*
> * We set b_transaction here because b_next_transaction will inherit
> * our jh reference and thus __jbd2_journal_file_buffer() must not
> --
> 2.21.3
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2020-06-17 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 9:10 [PATCH] jbd2: make sure jh have b_transaction set in refile/unlink_buffer Lukas Czerner
2020-06-17 9:25 ` [PATCH v2] jbd2: make sure jh have b_transaction set in refile/unfile_buffer Lukas Czerner
2020-06-17 12:15 ` Jan Kara [this message]
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=20200617121500.GA29763@quack2.suse.cz \
--to=jack@suse.cz \
--cc=jack@suse.com \
--cc=lczerner@redhat.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).