From: Avinesh Kumar via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/ioctl03: add IFF_BACKPRESSURE flag
Date: Wed, 2 Sep 2026 15:40:18 +0200 [thread overview]
Message-ID: <20260902134019.163296-1-avinesh.kumar@suse.com> (raw)
From: Avinesh Kumar <avinesh.kumar@suse.com>
Kernel commit 485e38995cc3 ("tun/tap: add IFF_BACKPRESSURE flag")
introduced a new TUNSETIFF flag, and d00c7369ef24 ("tun/tap &
vhost-net: stop tail-drop when IFF_BACKPRESSURE is set") added it
to TUN_FEATURES. TUNGETFEATURES now reports bit 0x80 on kernels
that support it, which ioctl03 does not recognize and reports as:
ioctl03.c:90: TFAIL: (UNKNOWN 0x80)
Add IFF_BACKPRESSURE to the known flags table.
Signed-off-by: Avinesh Kumar <avinesh.kumar@suse.com>
---
testcases/kernel/syscalls/ioctl/ioctl03.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/testcases/kernel/syscalls/ioctl/ioctl03.c b/testcases/kernel/syscalls/ioctl/ioctl03.c
index 8a868a98e605..1f538016344c 100644
--- a/testcases/kernel/syscalls/ioctl/ioctl03.c
+++ b/testcases/kernel/syscalls/ioctl/ioctl03.c
@@ -44,6 +44,10 @@
#define IFF_NO_CARRIER 0x0040
#endif
+#ifndef IFF_BACKPRESSURE
+#define IFF_BACKPRESSURE 0x0080
+#endif
+
static struct {
unsigned int flag;
const char *name;
@@ -56,7 +60,8 @@ static struct {
{IFF_MULTI_QUEUE, "MULTI_QUEUE"},
{IFF_NAPI, "IFF_NAPI"},
{IFF_NAPI_FRAGS, "IFF_NAPI_FRAGS"},
- {IFF_NO_CARRIER, "IFF_NO_CARRIER"}
+ {IFF_NO_CARRIER, "IFF_NO_CARRIER"},
+ {IFF_BACKPRESSURE, "IFF_BACKPRESSURE"}
};
static void verify_features(void)
--
2.55.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2026-09-02 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 13:40 Avinesh Kumar via ltp [this message]
2026-09-02 17:42 ` [LTP] syscalls/ioctl03: add IFF_BACKPRESSURE flag linuxtestproject.agent
2026-09-03 13:06 ` [LTP] [PATCH] " Andrea Cervesato via ltp
2026-09-03 13:07 ` Andrea Cervesato via ltp
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=20260902134019.163296-1-avinesh.kumar@suse.com \
--to=ltp@lists.linux.it \
--cc=avinesh.kumar@suse.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