From: "Riccardo Paolo Bestetti" <pbl@bestov.io>
To: "Jakub Kicinski" <kuba@kernel.org>
Cc: <davem@davemloft.net>, <cmllamas@google.com>,
<yoshfuji@linux-ipv6.org>, <dsahern@kernel.org>,
<edumazet@google.com>, <pabeni@redhat.com>,
<kernel-team@android.com>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <linmiaohe@huawei.com>
Subject: Re: NEEDS FIXING - Was: Re: [PATCH v2] ipv4: ping: fix bind address validity check
Date: Sat, 18 Jun 2022 09:36:16 +0200 [thread overview]
Message-ID: <CKT35VBLVILO.1RPVCE81R8RJJ@enhorning> (raw)
In-Reply-To: <20220617195816.53a2f2cf@kernel.org>
On Sat Jun 18, 2022 at 4:58 AM CEST, Jakub Kicinski wrote:
> On Sat, 18 Jun 2022 02:32:55 +0200 Riccardo Paolo Bestetti wrote:
> > [...]
> > 2) My patch is faulty. I had a complete and tested patch, including code
> > fixing the regression. Instead of sending it, however, I decided to
> > adapt it to preserve Carlos Llamas' version of ping.c, since they posted
> > their patch first. In doing so I used a work branch which contained a
> > faulty version (wrong flags) of the regression tests. The resulting
> > faulty patch is, unfortunately, currently in the tree.
> >
> > At this point, due to the unfortunate combination of (1) and (2), it
> > might be worth reverting the patch altogether and just applying the v1
> > (i.e. without the regression tests) to the tree and to the relevant LTS
> > versions.
>
> IIUC only the test is faulty / unreliable, correct?
Correct, I don't see anything wrong with the fix itself. When manually
tested it shows the intended behaviour (sorry for the long lines):
$ pwd
$KERNEL_TREE/net/tools/testing/selftests/net
$ uname -a
Linux enhorning 5.19.0-rc2kbr-00103-gb4a028c4d031 #1 SMP PREEMPT_DYNAMIC Fri Jun 17 13:51:24 CEST 2022 x86_64 GNU/Linux
$ ./nettest -s -D -P icmp -l 224.0.0.1 -b
09:19:50 server: error binding socket: 99: Cannot assign requested address
$ ./nettest -s -D -P icmp -l 255.255.255.255 -b
09:21:20 server: error binding socket: 99: Cannot assign requested address
(and fcnal-test.sh shows nothing noteworthy.)
Riccardo P. Bestetti
>
> We have until Thursday before this patch hits Linus's tree so should
> be plenty of time to figure the problem out and apply an incremental
> fix. I see you posted an RFC already, thanks!
>
> > After that, a more proper discussion can be had about (1), and the
> > regression tests can be fixed. I'm sending a demonstrative patch for
> > that as a response to this message.
next prev parent reply other threads:[~2022-06-18 7:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 8:54 [PATCH v2] ipv4: ping: fix bind address validity check Riccardo Paolo Bestetti
2022-06-17 11:30 ` patchwork-bot+netdevbpf
2022-06-17 23:45 ` Maciej Żenczykowski
2022-06-20 10:11 ` Greg KH
2022-06-23 18:18 ` Maciej Żenczykowski
2022-06-25 14:26 ` Greg KH
2022-06-18 0:32 ` NEEDS FIXING - Was: " Riccardo Paolo Bestetti
2022-06-18 2:58 ` Jakub Kicinski
2022-06-18 7:36 ` Riccardo Paolo Bestetti [this message]
2022-06-19 16:44 ` Riccardo Paolo Bestetti
2022-06-17 16:39 ` Carlos Llamas
2022-06-17 18:26 ` Riccardo Paolo Bestetti
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=CKT35VBLVILO.1RPVCE81R8RJJ@enhorning \
--to=pbl@bestov.io \
--cc=cmllamas@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kernel-team@android.com \
--cc=kuba@kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.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