Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: stable@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH 6.1.y] selftests: mptcp: diag: skip listen tests if not supported
Date: Thu, 22 Jun 2023 19:13:05 +0200	[thread overview]
Message-ID: <2023062256-salary-glorified-e5c0@gregkh> (raw)
In-Reply-To: <6f9987c8-dcdb-6938-9bae-82605162acd4@tessares.net>

On Thu, Jun 22, 2023 at 04:06:22PM +0200, Matthieu Baerts wrote:
> Hi Greg,
> 
> On 22/06/2023 11:19, Greg KH wrote:
> > On Thu, Jun 22, 2023 at 11:08:52AM +0200, Matthieu Baerts wrote:
> >> commit dc97251bf0b70549c76ba261516c01b8096771c5 upstream.
> >>
> >> Selftests are supposed to run on any kernels, including the old ones not
> >> supporting all MPTCP features.
> >>
> >> One of them is the listen diag dump support introduced by
> >> commit 4fa39b701ce9 ("mptcp: listen diag dump support").
> >>
> >> It looks like there is no good pre-check to do here, i.e. dedicated
> >> function available in kallsyms. Instead, we try to get info if nothing
> >> is returned, the test is marked as skipped.
> >>
> >> That's not ideal because something could be wrong with the feature and
> >> instead of reporting an error, the test could be marked as skipped. If
> >> we know in advanced that the feature is supposed to be supported, the
> >> tester can set SELFTESTS_MPTCP_LIB_EXPECT_ALL_FEATURES env var to 1: in
> >> this case the test will report an error instead of marking the test as
> >> skipped if nothing is returned.
> >>
> >> Link: https://github.com/multipath-tcp/mptcp_net-next/issues/368
> >> Fixes: f2ae0fa68e28 ("selftests/mptcp: add diag listen tests")
> >> Cc: stable@vger.kernel.org
> >> Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
> >> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> >> Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
> >> ---
> >> Applied on top of stable-rc/linux-6.1.y: 639ecee7e0d3 ("Linux 6.1.36-rc1")
> >> Conflicting with commit e04a30f78809 ("selftest: mptcp: add test for
> >> mptcp socket in use"): modifications around __chk_msk_nr() have been
> >> included here.
> >> ---
> >>  tools/testing/selftests/net/mptcp/diag.sh | 47 ++++++++++++-----------
> >>  1 file changed, 24 insertions(+), 23 deletions(-)
> >>
> > 
> > Now queued up, thanks.
> 
> Thank you for having already queued this patch and all the other ones
> from Linus' tree!
> 
> I just sent the last patches fixing conflicts in v5.10. I don't have any
> others linked to MPTCP and I replied to the ones that don't need to be
> backported to older versions than v6.1.
> 

Thanks, I think I got them all now!

greg k-h

  reply	other threads:[~2023-06-22 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22  7:56 FAILED: patch "[PATCH] selftests: mptcp: diag: skip listen tests if not supported" failed to apply to 6.1-stable tree gregkh
2023-06-22  9:08 ` [PATCH 6.1.y] selftests: mptcp: diag: skip listen tests if not supported Matthieu Baerts
2023-06-22  9:19   ` Greg KH
2023-06-22 14:06     ` Matthieu Baerts
2023-06-22 17:13       ` Greg KH [this message]
2023-06-22 17:22         ` Matthieu Baerts

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=2023062256-salary-glorified-e5c0@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=matthieu.baerts@tessares.net \
    --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