From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, kuniyu@amazon.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH stable 5.15/6.1/6.6] af_unix: Clear oob_skb in scan_inflight().
Date: Tue, 4 Mar 2025 17:13:52 -0500 [thread overview]
Message-ID: <20250304142915-28afde2108e0471d@stable.kernel.org> (raw)
In-Reply-To: <20250304030149.82265-1-kuniyu@amazon.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Could not find matching upstream commit
No upstream commit was identified. Using temporary commit for testing.
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
| stable/linux-6.1.y | Success | Success |
| stable/linux-6.6.y | Success | Success |
next prev parent reply other threads:[~2025-03-04 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 3:01 [PATCH stable 5.15/6.1/6.6] af_unix: Clear oob_skb in scan_inflight() Kuniyuki Iwashima
2025-03-04 22:13 ` Sasha Levin [this message]
2025-03-05 14:08 ` Greg Kroah-Hartman
2025-03-05 18:10 ` Kuniyuki Iwashima
2025-03-05 18:22 ` Greg KH
2025-05-12 7:53 ` Lee Jones
2025-05-16 8:18 ` Lee Jones
2025-05-16 18:27 ` [PATCH Astable " Kuniyuki Iwashima
2025-04-29 11:12 ` [PATCH stable " Lee Jones
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=20250304142915-28afde2108e0471d@stable.kernel.org \
--to=sashal@kernel.org \
--cc=kuniyu@amazon.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