From: Jakub Kicinski <kuba@kernel.org>
To: Petr Machata <petrm@nvidia.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v3 7/7] selftests: net: fdb_notify: Add a test for FDB notifications
Date: Wed, 13 Nov 2024 17:08:41 -0800 [thread overview]
Message-ID: <20241113170841.7acf33de@kernel.org> (raw)
In-Reply-To: <871pzfjgc2.fsf@nvidia.com>
On Wed, 13 Nov 2024 16:11:03 +0100 Petr Machata wrote:
> > - A "0 seen, 1 expected", which... I don't know, maybe it could just be
> > a misplaced sleep. I don't see how, but it's a deterministing
> > scenario, there shouldn't be anything racy here, either it emits or it
> > doesn't, so some buffering issue is the only thing I can think of.
>
> I think this really could be just a "bridge monitor" taking a bit more
> time to start every now and then. Can I have you test with this extra
> chunk, or should I just resend with that change and hope for the best?
Let's give it a go, if it doesn't fix it we can try to do sneaky local
changes in the CI, without more resends.
prev parent reply other threads:[~2024-11-14 1:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 17:08 [PATCH net-next v3 0/7] net: ndo_fdb_add/del: Have drivers report whether they notified Petr Machata
2024-11-11 17:08 ` [PATCH net-next v3 1/7] ndo_fdb_add: Add a parameter to report whether notification was sent Petr Machata
2024-11-11 17:08 ` [Intel-wired-lan] " Petr Machata
2024-11-12 13:56 ` Nikolay Aleksandrov
2024-11-12 13:56 ` [Intel-wired-lan] " Nikolay Aleksandrov
2024-11-11 17:08 ` [PATCH net-next v3 2/7] ndo_fdb_del: " Petr Machata
2024-11-11 17:08 ` [Intel-wired-lan] " Petr Machata
2024-11-12 13:56 ` Nikolay Aleksandrov
2024-11-12 13:56 ` [Intel-wired-lan] " Nikolay Aleksandrov
2024-11-11 17:08 ` [PATCH net-next v3 3/7] selftests: net: lib: Move logging from forwarding/lib.sh here Petr Machata
2024-11-11 17:08 ` [PATCH net-next v3 4/7] selftests: net: lib: Move tests_run " Petr Machata
2024-11-11 17:08 ` [PATCH net-next v3 5/7] selftests: net: lib: Move checks " Petr Machata
2024-11-11 17:09 ` [PATCH net-next v3 6/7] selftests: net: lib: Add kill_process Petr Machata
2024-11-11 17:09 ` [PATCH net-next v3 7/7] selftests: net: fdb_notify: Add a test for FDB notifications Petr Machata
2024-11-12 22:22 ` Jakub Kicinski
2024-11-13 11:46 ` Petr Machata
2024-11-13 15:11 ` Petr Machata
2024-11-14 1:08 ` Jakub Kicinski [this message]
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=20241113170841.7acf33de@kernel.org \
--to=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.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.