From: kernel test rebot <yi1.lai@intel.com>
To: Simon Schippers <simon.schippers@tu-dortmund.de>
Cc: lkp@intel.com, netdev@vger.kernel.org,
Tim Gebauer <tim.gebauer@tu-dortmund.de>,
yi1.lai@intel.com, oe-lkp@lists.linux.dev,
Jakub Kicinski <kuba@kernel.org>,
ltp@lists.linux.it
Subject: Re: [LTP] [linux-next:master] [tun/tap & vhost] d00c7369ef: ltp.ioctl03.fail
Date: Mon, 17 Aug 2026 16:06:24 +0800 [thread overview]
Message-ID: <aoLBAPxcXXG+i90Q@ly-workstation> (raw)
In-Reply-To: <bf700b2d-4593-41ee-bac2-6438b65e3720@tu-dortmund.de>
On Mon, Aug 17, 2026 at 09:39:26AM +0200, Simon Schippers wrote:
> On 8/17/26 03:34, kernel test robot wrote:
> >
> >
> > Hello,
> >
> > kernel test robot noticed "ltp.ioctl03.fail" on:
> >
> > commit: d00c7369ef24ac8e0383de0fd8ef3384de20bcfa ("tun/tap & vhost-net: stop tail-drop when IFF_BACKPRESSURE is set") https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> >
> > [test failed on linux-next/master 4477a78374a57c3809b172ad30cceabda48c47c6]
> > ────────────────────────
> > TEST SUMMARY
> > ────────────────────────
> > Suite: syscalls-03
> > Runtime: 3m 4s
> > Runs: 186
> >
> > Results:
> > Passed: 2174
> > Failed: 1
> > Broken: 0
> > Skipped: 222
> > Warnings: 0
> >
> > [1;31mFailures: [0m
> > • ioctl03
>
> The same harmless report as before:
>
> ioctl03.c does not know about IFF_BACKPRESSURE which is introduced here,
> consequently it fails.
> See [1] where it compares TUN features with known_flags.
>
> Thanks.
Thanks for the response. I just noticed that it's reported before. Sorry
for the duplication.
>
> [1] Link: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/ioctl/ioctl03.c#L82
>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-08-17 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 1:34 [LTP] [linux-next:master] [tun/tap & vhost] d00c7369ef: ltp.ioctl03.fail kernel test robot
[not found] ` <bf700b2d-4593-41ee-bac2-6438b65e3720@tu-dortmund.de>
2026-08-17 8:06 ` kernel test rebot [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=aoLBAPxcXXG+i90Q@ly-workstation \
--to=yi1.lai@intel.com \
--cc=kuba@kernel.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=simon.schippers@tu-dortmund.de \
--cc=tim.gebauer@tu-dortmund.de \
/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