From: Jakub Kicinski <kuba@kernel.org>
To: Yizhou Zhao <zhaoyz24@mails.tsinghua.edu.cn>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3 RESEND] net/dccp: validate Reset/Close/CloseReq in DCCP_REQUESTING
Date: Mon, 3 Nov 2025 15:44:39 -0800 [thread overview]
Message-ID: <20251103154439.58c3664c@kernel.org> (raw)
In-Reply-To: <20251103021557.4020515-1-zhaoyz24@mails.tsinghua.edu.cn>
On Mon, 3 Nov 2025 10:15:57 +0800 Yizhou Zhao wrote:
> Following your instruction, we read the documentation at https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html.
> We found that the stable documentation normally requires an upstream
> commit before inclusion in stable, but here an upstream commit cannot
> exist because the subsystem was removed. Could you please confirm
> that this can proceed as a stable-only fix for the affected LTS
> branches?
Yes.
prev parent reply other threads:[~2025-11-03 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 5:45 [PATCH v3 RESEND] net/dccp: validate Reset/Close/CloseReq in DCCP_REQUESTING Yizhou Zhao
2025-11-02 23:54 ` Jakub Kicinski
2025-11-03 1:11 ` Yizhou Zhao
2025-11-03 2:15 ` Yizhou Zhao
2025-11-03 23:44 ` Jakub Kicinski [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=20251103154439.58c3664c@kernel.org \
--to=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=zhaoyz24@mails.tsinghua.edu.cn \
/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;
as well as URLs for NNTP newsgroup(s).