Hi Jiayuan,
On 30/11/2025 04:23, Jiayuan Chen wrote:
Overall, we encountered a warning [1] that can be triggered by running the selftest I provided.
Thank you for having shared these patches, but there are some issues with them:
- Patch 1/2 has already been queued, see [1].
- Patch 2/2 is the exact same patch as the one sent by Sasha [2], and recently dropped [3] because it breaks MPTCP. See my comment there.
- You need to follow the stable rules [4] when sending patches to stable. In short, here, you should have kept the original upstream commit message, then add the SHA and a note about the conflicts, e.g. similar to [5]. Without that, it is a new patch, not a backport (and the reviewed-by/acked-by/... cannot be kept).
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree... [2] https://lore.kernel.org/stable/9e6ef98f-12eb-4608-aece-cf321e0a38d7@kernel.o... [3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/comm... [4] https://docs.kernel.org/process/stable-kernel-rules.html [5] https://lore.kernel.org/stable/20251129165612.2125498-2-matttbe@kernel.org/T...
Cheers, Matt