From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Safonov <0x7f454c46@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [TEST] TCP MD5 vs kmemleak
Date: Mon, 17 Jun 2024 07:24:51 -0700 [thread overview]
Message-ID: <20240617072451.1403e1d2@kernel.org> (raw)
Hi Dmitry!
We added kmemleak checks to the selftest runners, TCP AO/MD5 tests seem
to trip it:
https://netdev-3.bots.linux.dev/vmksft-tcp-ao-dbg/results/643761/4-unsigned-md5-ipv6/stdout
Could you take a look? kmemleak is not infallible, it could be a false
positive.
next reply other threads:[~2024-06-17 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 14:24 Jakub Kicinski [this message]
2024-06-18 3:24 ` [TEST] TCP MD5 vs kmemleak Dmitry Safonov
2024-06-18 14:40 ` Jakub Kicinski
2024-06-18 16:17 ` Paul E. McKenney
2024-06-18 16:30 ` Paolo Abeni
2024-06-18 16:42 ` Paul E. McKenney
2024-06-18 17:02 ` Jakub Kicinski
2024-06-18 17:04 ` Uladzislau Rezki
2024-06-18 17:47 ` Paul E. McKenney
2024-06-19 0:33 ` Dmitry Safonov
2024-06-20 17:02 ` Paul E. McKenney
2024-07-02 2:08 ` Dmitry Safonov
2024-07-08 11:05 ` Catalin Marinas
2024-07-08 18:29 ` Paul E. McKenney
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=20240617072451.1403e1d2@kernel.org \
--to=kuba@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).