Netdev List
 help / color / mirror / Atom feed
From: Simon Schippers <simon.schippers@tu-dortmund.de>
To: kernel test robot <yi1.lai@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	Jakub Kicinski <kuba@kernel.org>,
	Tim Gebauer <tim.gebauer@tu-dortmund.de>,
	netdev@vger.kernel.org, ltp@lists.linux.it
Subject: Re: [linux-next:master] [tun/tap & vhost] d00c7369ef: ltp.ioctl03.fail
Date: Mon, 17 Aug 2026 09:39:26 +0200	[thread overview]
Message-ID: <bf700b2d-4593-41ee-bac2-6438b65e3720@tu-dortmund.de> (raw)
In-Reply-To: <202608170325.fbd7c808-lkp@intel.com>

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.

[1] Link: https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/ioctl/ioctl03.c#L82


  reply	other threads:[~2026-08-17  7:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  1:34 [linux-next:master] [tun/tap & vhost] d00c7369ef: ltp.ioctl03.fail kernel test robot
2026-08-17  7:39 ` Simon Schippers [this message]
2026-08-17  8:06   ` kernel test rebot

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=bf700b2d-4593-41ee-bac2-6438b65e3720@tu-dortmund.de \
    --to=simon.schippers@tu-dortmund.de \
    --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=tim.gebauer@tu-dortmund.de \
    --cc=yi1.lai@intel.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