From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Keerthana K <keerthana.kalyanasundaram@broadcom.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v5.10-v6.6] btrfs: don't BUG_ON on ENOMEM from btrfs_lookuip_extent_info() in walk_down_proc()
Date: Fri, 6 Dec 2024 12:11:30 -0500 [thread overview]
Message-ID: <20241206112129-3501fbcbea4a5d21@stable.kernel.org> (raw)
In-Reply-To: <20241206040846.4013310-1-keerthana.kalyanasundaram@broadcom.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: a580fb2c3479d993556e1c31b237c9e5be4944a3
WARNING: Author mismatch between patch and upstream commit:
Backport author: Keerthana K <keerthana.kalyanasundaram@broadcom.com>
Commit author: Josef Bacik <josef@toxicpanda.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: a580fb2c3479d < -: ------------- btrfs: don't BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc()
-: ------------- > 1: 614d01a4521eb btrfs: don't BUG_ON on ENOMEM from btrfs_lookuip_extent_info() in walk_down_proc()
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
| stable/linux-5.10.y | Success | Success |
prev parent reply other threads:[~2024-12-06 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 4:08 [PATCH v5.10-v6.6] btrfs: don't BUG_ON on ENOMEM from btrfs_lookuip_extent_info() in walk_down_proc() Keerthana K
2024-12-06 17:11 ` 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=20241206112129-3501fbcbea4a5d21@stable.kernel.org \
--to=sashal@kernel.org \
--cc=keerthana.kalyanasundaram@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox