From: Vastargazing <vebohr@gmail.com>
To: matttbe@kernel.org
Cc: martineau@kernel.org, mptcp@lists.linux.dev,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org, stable@vger.kernel.org, fw@strlen.de
Subject: Re: [PATCH] selftests: mptcp: add test for IPv6 subflow SLAB placement
Date: Fri, 1 May 2026 20:01:36 +0300 [thread overview]
Message-ID: <20260501-reply-mptcp-v6-initcall@vebohr> (raw)
In-Reply-To: <44e564f8-d059-407b-8f5e-a149dd76dea3@kernel.org>
Hi Matt,
Thanks for the review (and for cc'ing Florian - same mistake twice, noted).
You're right on both. The 755 thing is on me, and i'm convinced the
standalone script is too much for what's essentially a one-time init
ordering issue - the fix commit is the safety net here.
Withdrawing the patch.
One question if you don't mind: if something similar came up again and
a test *was* warranted, which existing script would be the natural
home? mptcp_join.sh seemed closest since it exercises the accept path,
but i'm not sure if checking /proc/slabinfo fits there or if there's a
better mechanism for that kind of thing.
Vastargazing
next prev parent reply other threads:[~2026-05-01 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 15:14 [PATCH] selftests: mptcp: add test for IPv6 subflow SLAB placement Vastargazing
2026-05-01 15:45 ` Matthieu Baerts
2026-05-01 17:01 ` Vastargazing [this message]
2026-05-04 17:44 ` 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=20260501-reply-mptcp-v6-initcall@vebohr \
--to=vebohr@gmail.com \
--cc=fw@strlen.de \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--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