Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Anand Jain <anajain.sg@gmail.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: remove duplicate journal_info reset on failure to commit transaction
Date: Thu, 2 Apr 2026 12:56:58 +0800	[thread overview]
Message-ID: <f5185c25-c235-46f0-80ec-7ad2b7426d26@gmail.com> (raw)
In-Reply-To: <fa5c062786a6a987ffc2643fc444ab9c106fbeb0.1775069670.git.fdmanana@suse.com>


Looks good.

Reviewed-by: Anand Jain <asj@kernel.org>




On 2/4/26 02:55, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> If we get an error during the transaction commit path, we are resetting
> current->journal_info to NULL twice - once in btrfs_commit_transaction()
> right before calling cleanup_transaction() and then once again inside
> cleanup_transaction(). Remove the instance in btrfs_commit_transaction().
> 
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
>  fs/btrfs/transaction.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c
> index c9c316ce4bdc..248adb785051 100644
> --- a/fs/btrfs/transaction.c
> +++ b/fs/btrfs/transaction.c
> @@ -2657,8 +2657,6 @@ int btrfs_commit_transaction(struct btrfs_trans_handle *trans)
>  	btrfs_trans_release_chunk_metadata(trans);
>  	trans->block_rsv = NULL;
>  	btrfs_warn(fs_info, "Skipping commit of aborted transaction.");
> -	if (current->journal_info == trans)
> -		current->journal_info = NULL;
>  	cleanup_transaction(trans, ret);
>  
>  	return ret;


      reply	other threads:[~2026-04-02  4:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 18:55 [PATCH] btrfs: remove duplicate journal_info reset on failure to commit transaction fdmanana
2026-04-02  4:56 ` Anand Jain [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=f5185c25-c235-46f0-80ec-7ad2b7426d26@gmail.com \
    --to=anajain.sg@gmail.com \
    --cc=fdmanana@kernel.org \
    --cc=linux-btrfs@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