From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, superman.xpt@gmail.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v2 6.14.y] btrfs: fix the inode leak in btrfs_iget()
Date: Thu, 8 May 2025 12:18:21 -0400 [thread overview]
Message-ID: <20250507080609-a1af134a5ce3061d@stable.kernel.org> (raw)
In-Reply-To: <20250505150322.40733-1-superman.xpt@gmail.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: 48c1d1bb525b1c44b8bdc8e7ec5629cb6c2b9fc4
Note: The patch differs from the upstream commit:
---
1: 48c1d1bb525b1 < -: ------------- btrfs: fix the inode leak in btrfs_iget()
-: ------------- > 1: aeaee199900ee Linux 6.14.5
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.14.y | Success | Success |
prev parent reply other threads:[~2025-05-08 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 7:41 FAILED: patch "[PATCH] btrfs: fix the inode leak in btrfs_iget()" failed to apply to 6.14-stable tree gregkh
2025-05-05 15:03 ` [PATCH v2 6.14.y] btrfs: fix the inode leak in btrfs_iget() Penglei Jiang
2025-05-07 9:23 ` Greg KH
2025-05-08 16:18 ` 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=20250507080609-a1af134a5ce3061d@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=superman.xpt@gmail.com \
/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