From: Greg KH <gregkh@linuxfoundation.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Fred Klassen <fklassen@appneta.com>
Subject: Re: 4.19: udpgso_bench_tx: setsockopt zerocopy: Unknown error 524
Date: Tue, 18 Jun 2019 18:10:36 +0200 [thread overview]
Message-ID: <20190618161036.GA28190@kroah.com> (raw)
In-Reply-To: <CA+FuTSfBFqRViKfG5crEv8xLMgAkp3cZ+yeuELK5TVv61xT=Yw@mail.gmail.com>
On Tue, Jun 18, 2019 at 08:31:16AM -0400, Willem de Bruijn wrote:
> On Tue, Jun 18, 2019 at 7:27 AM Naresh Kamboju
> <naresh.kamboju@linaro.org> wrote:
> >
> > selftests: net: udpgso_bench.sh failed on 4.19, 4.14, 4.9 and 4.4 branches.
> > PASS on stable branch 5.1, mainline and next.
> > This failure is started happening on 4.19 and older kernel branches after
> > kselftest upgrade to version 5.1
>
> Does version 5.1 here mean running tests from Linux 5.1, against older kernels?
>
> > Is there any possibilities to backport ?
> >
> > Error:
> > udpgso_bench_tx: setsockopt zerocopy: Unknown error 524
>
> MSG_ZEROCOPY for UDP was added in commit b5947e5d1e71 ("udp:
> msg_zerocopy") in Linux 5.0.
>
> The selftest was expanded with this feature in commit db63e489c7aa
> ("selftests: extend zerocopy tests to udp"), also in Linux 5.0.
>
> Those tests are not expected to pass on older kernels.
Any way to degrade gracefully if the feature is not present at all in
the kernel under test? People run the latest version of kselftests on
older kernels all the time.
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-18 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 11:27 4.19: udpgso_bench_tx: setsockopt zerocopy: Unknown error 524 Naresh Kamboju
2019-06-18 12:31 ` Willem de Bruijn
2019-06-18 16:10 ` Greg KH [this message]
2019-06-18 16:37 ` Willem de Bruijn
2019-06-18 16:47 ` David Miller
2019-06-18 17:15 ` Greg KH
2019-06-18 17:27 ` Willem de Bruijn
2019-06-18 17:39 ` Greg KH
2019-06-18 18:58 ` Willem de Bruijn
2019-06-18 20:04 ` Willem de Bruijn
2019-06-18 22:44 ` David Miller
2019-06-19 0:38 ` Willem de Bruijn
2019-06-18 17:37 ` David Miller
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=20190618161036.GA28190@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=fklassen@appneta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
/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).