Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Kenta Akagi <k@mgml.me>, gregkh@linuxfoundation.org, sashal@kernel.org
Cc: stable@vger.kernel.org, MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH 6.1.y] selftests: mptcp: connect: fix build regression caused by backport
Date: Thu, 2 Oct 2025 20:54:22 +0200	[thread overview]
Message-ID: <77d23523-be4d-4c5a-aa54-8617e7b5e6e2@kernel.org> (raw)
In-Reply-To: <20251002141759.76891-1-k@mgml.me>

Hi Kenta,

On 02/10/2025 16:17, Kenta Akagi wrote:
> Since v6.1.154, mptcp selftests have failed to build with the following
> errors:
> 
> mptcp_connect.c: In function ‘main_loop_s’:
> mptcp_connect.c:1040:59: error: ‘winfo’ undeclared (first use in this function)
>  1040 |                 err = copyfd_io(fd, remotesock, 1, true, &winfo);
>       |                                                           ^~~~~
> mptcp_connect.c:1040:59: note: each undeclared identifier is reported only once for each function it appears in
> mptcp_connect.c:1040:23: error: too many arguments to function ‘copyfd_io’; expected 4, have 5
>  1040 |                 err = copyfd_io(fd, remotesock, 1, true, &winfo);
>       |                       ^~~~~~~~~                          ~~~~~~
> mptcp_connect.c:845:12: note: declared here
>   845 | static int copyfd_io(int infd, int peerfd, int outfd, bool close_peerfd)
>       |            ^~~~~~~~~
> 
> This is caused by commit ff160500c499 ("selftests: mptcp: connect: catch
> IO errors on listen side"), a backport of upstream 14e22b43df25,
> which attempts to use the undeclared variable 'winfo' and passes too many
> arguments to copyfd_io(). Both the winfo variable and the updated
> copyfd_io() function were introduced in upstream
> commit ca7ae8916043 ("selftests: mptcp: mptfo Initiator/Listener"),
> which is not present in v6.1.y.
> 
> The goal of the backport is to stop on errors from copyfd_io.
> Therefore, the backport does not depend on the changes in upstream
> commit ca7ae8916043 ("selftests: mptcp: mptfo Initiator/Listener").
> 
> This commit simply removes ', &winfo' to fix a build failure.

Thank you for this fix for v6.1.y!

Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


      reply	other threads:[~2025-10-02 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 14:17 [PATCH 6.1.y] selftests: mptcp: connect: fix build regression caused by backport Kenta Akagi
2025-10-02 18:54 ` Matthieu Baerts [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=77d23523-be4d-4c5a-aa54-8617e7b5e6e2@kernel.org \
    --to=matttbe@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=k@mgml.me \
    --cc=mptcp@lists.linux.dev \
    --cc=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