Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y 1/3] selftests: mptcp: make sendfile selftest work
Date: Wed, 30 Jul 2025 12:28:49 -0400	[thread overview]
Message-ID: <1753887608-a99f9044@stable.kernel.org> (raw)
In-Reply-To: <20250730102806.1405622-6-matttbe@kernel.org>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: df9e03aec3b14970df05b72d54f8ac9da3ab29e1

WARNING: Author mismatch between patch and upstream commit:
Backport author: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Commit author: Florian Westphal <fw@strlen.de>

Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (exact SHA1)

Note: The patch differs from the upstream commit:
---
1:  df9e03aec3b1 ! 1:  2b0b67ac1f24 selftests: mptcp: make sendfile selftest work
    @@ Metadata
      ## Commit message ##
         selftests: mptcp: make sendfile selftest work
     
    +    commit df9e03aec3b14970df05b72d54f8ac9da3ab29e1 upstream.
    +
         When the selftest got added, sendfile() on mptcp sockets returned
         -EOPNOTSUPP, so running 'mptcp_connect.sh -m sendfile' failed
         immediately.
    @@ Commit message
         Signed-off-by: Florian Westphal <fw@strlen.de>
         Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
         Signed-off-by: David S. Miller <davem@davemloft.net>
    +    Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
     
      ## tools/testing/selftests/net/mptcp/mptcp_connect.c ##
    -@@ tools/testing/selftests/net/mptcp/mptcp_connect.c: static void set_nonblock(int fd, bool nonblock)
    - 		fcntl(fd, F_SETFL, flags & ~O_NONBLOCK);
    +@@ tools/testing/selftests/net/mptcp/mptcp_connect.c: static void set_nonblock(int fd)
    + 	fcntl(fd, F_SETFL, flags | O_NONBLOCK);
      }
      
     +static void shut_wr(int fd)

---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| 5.15                      | Success     | Success    |

  reply	other threads:[~2025-07-30 16:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 13:48 FAILED: patch "[PATCH] selftests: mptcp: connect: also cover alt modes" failed to apply to 5.15-stable tree gregkh
2025-07-29 14:20 ` [PATCH 5.15.y] selftests: mptcp: connect: also cover alt modes Sasha Levin
2025-07-29 14:32   ` Matthieu Baerts
2025-07-29 14:36     ` Sasha Levin
2025-07-30 10:28 ` [PATCH 5.15.y 0/3] mptcp: fix recent failed backports (20250728) Matthieu Baerts (NGI0)
2025-07-30 10:28 ` [PATCH 5.15.y 1/3] selftests: mptcp: make sendfile selftest work Matthieu Baerts (NGI0)
2025-07-30 16:28   ` Sasha Levin [this message]
2025-07-30 10:28 ` [PATCH 5.15.y 2/3] selftests: mptcp: connect: also cover alt modes Matthieu Baerts (NGI0)
2025-07-30 16:28   ` Sasha Levin
2025-07-30 16:41     ` Matthieu Baerts
2025-07-31  1:09       ` Sasha Levin
2025-07-31  9:28         ` Matthieu Baerts
2025-07-30 10:28 ` [PATCH 5.15.y 3/3] selftests: mptcp: connect: also cover checksum Matthieu Baerts (NGI0)
2025-07-30 16:28   ` Sasha Levin

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=1753887608-a99f9044@stable.kernel.org \
    --to=sashal@kernel.org \
    --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