From: Cyril Hrubis <chrubis@suse.cz>
To: Eric Dumazet <edumazet@google.com>
Cc: Kuniyuki Iwashima <kuniyu@google.com>,
lkp@intel.com, netdev@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>,
oe-lkp@lists.linux.dev, Jakub Kicinski <kuba@kernel.org>,
ltp@lists.linux.it
Subject: Re: [LTP] [linux-next:master] [icmp] 64db5933c7: ltp.cve-2020-25705.fail
Date: Wed, 11 Mar 2026 11:33:08 +0100 [thread overview]
Message-ID: <abFE5PEtrkT5paKB@yuki.lan> (raw)
In-Reply-To: <CANn89iKUdtWw4ptM8ZreRP0a2FuvQOJ5FgE3o4q-zTRTmt1Umg@mail.gmail.com>
Hi!
> I do not want to know what this test is doing or expecting.
>
> If it expects sysctls to have a precise value, it should set them ?
The test is a CVE reproducer that checks if ICMP message ratelimiting is
sufficiently randomized so that we do not leak information about the
system.
See the test source code:
https://github.com/linux-test-project/ltp/blob/master/testcases/cve/icmp_rate_limit01.c
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: Eric Dumazet <edumazet@google.com>
Cc: kernel test robot <oliver.sang@intel.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
lkp@intel.com, netdev@vger.kernel.org, oe-lkp@lists.linux.dev,
Jakub Kicinski <kuba@kernel.org>,
ltp@lists.linux.it
Subject: Re: [LTP] [linux-next:master] [icmp] 64db5933c7: ltp.cve-2020-25705.fail
Date: Wed, 11 Mar 2026 11:33:08 +0100 [thread overview]
Message-ID: <abFE5PEtrkT5paKB@yuki.lan> (raw)
In-Reply-To: <CANn89iKUdtWw4ptM8ZreRP0a2FuvQOJ5FgE3o4q-zTRTmt1Umg@mail.gmail.com>
Hi!
> I do not want to know what this test is doing or expecting.
>
> If it expects sysctls to have a precise value, it should set them ?
The test is a CVE reproducer that checks if ICMP message ratelimiting is
sufficiently randomized so that we do not leak information about the
system.
See the test source code:
https://github.com/linux-test-project/ltp/blob/master/testcases/cve/icmp_rate_limit01.c
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2026-03-11 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 6:42 [LTP] [linux-next:master] [icmp] 64db5933c7: ltp.cve-2020-25705.fail kernel test robot
2026-03-09 6:42 ` kernel test robot
2026-03-09 7:40 ` [LTP] " Eric Dumazet via ltp
2026-03-09 7:40 ` Eric Dumazet
2026-03-11 10:33 ` Cyril Hrubis [this message]
2026-03-11 10:33 ` [LTP] " Cyril Hrubis
2026-03-11 10:45 ` Eric Dumazet via ltp
2026-03-11 10:45 ` Eric Dumazet
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=abFE5PEtrkT5paKB@yuki.lan \
--to=chrubis@suse.cz \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=netdev@vger.kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.