All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: bin.lan.cn@windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] btrfs: do not clean up repair bio if submit fails
Date: Thu,  8 May 2025 21:52:10 -0400	[thread overview]
Message-ID: <20250508132012-dffd88be939cf54b@stable.kernel.org> (raw)
In-Reply-To: <20250508122355.99249-1-bin.lan.cn@windriver.com>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 8cbc3001a3264d998d6b6db3e23f935c158abd4d

WARNING: Author mismatch between patch and upstream commit:
Backport author: bin.lan.cn@windriver.com
Commit author: Josef Bacik<josef@toxicpanda.com>

Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (exact SHA1)

Note: The patch differs from the upstream commit:
---
1:  8cbc3001a3264 ! 1:  90c24cbc95555 btrfs: do not clean up repair bio if submit fails
    @@ Metadata
      ## Commit message ##
         btrfs: do not clean up repair bio if submit fails
     
    +    [ Upstream commit 8cbc3001a3264d998d6b6db3e23f935c158abd4d ]
    +
         The submit helper will always run bio_endio() on the bio if it fails to
         submit, so cleaning up the bio just leads to a variety of use-after-free
         and NULL pointer dereference bugs because we race with the endio
    @@ Commit message
         Reviewed-by: Boris Burkov <boris@bur.io>
         Signed-off-by: Josef Bacik <josef@toxicpanda.com>
         Signed-off-by: David Sterba <dsterba@suse.com>
    +    [Minor context change fixed.]
    +    Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
    +    Signed-off-by: He Zhe <zhe.he@windriver.com>
     
      ## fs/btrfs/extent_io.c ##
     @@ fs/btrfs/extent_io.c: int btrfs_repair_one_sector(struct inode *inode,
      	const int icsum = bio_offset >> fs_info->sectorsize_bits;
      	struct bio *repair_bio;
    - 	struct btrfs_bio *repair_bbio;
    + 	struct btrfs_io_bio *repair_io_bio;
     -	blk_status_t status;
      
      	btrfs_debug(fs_info,
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y       |  Success    |  Success   |

      reply	other threads:[~2025-05-09  1:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 12:23 [PATCH 5.15.y] btrfs: do not clean up repair bio if submit fails bin.lan.cn
2025-05-09  1:52 ` Sasha Levin [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=20250508132012-dffd88be939cf54b@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=bin.lan.cn@windriver.com \
    --cc=stable@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 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.