All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Machata <petrm@nvidia.com>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: Petr Machata <petrm@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, <netdev@vger.kernel.org>,
	Ido Schimmel <idosch@nvidia.com>,
	Andy Roulin <aroulin@nvidia.com>, <mlxsw@nvidia.com>
Subject: Re: [PATCH net-next] net: neighbour: Avoid sending RTM_NEWNEIGH for a dead neighbor
Date: Fri, 6 Nov 2026 16:39:56 +0100	[thread overview]
Message-ID: <87eccy2ckz.fsf@pmachata.org> (raw)
In-Reply-To: <auzmIrtt_gMVjWhs@google.com> (Kuniyuki Iwashima's message of "Thu, 5 Nov 2026 20:28:31 +0000")

Kuniyuki Iwashima <kuniyu@google.com> writes:

> On Wed, 04 Nov 2026 14:56:56 +0100, Petr Machata wrote:
>
>> --- a/net/core/neighbour.c
>> +++ b/net/core/neighbour.c
>> @@ -3593,6 +3593,13 @@ static void __neigh_notify(struct neighbour *n, int type, int flags,
>>  	int err = -ENOBUFS;
>>  	struct net *net;
>>  
>> +	/* An attempt to send anything but RTM_DELNEIGH on a dead neighbor
>> +	 * indicates that the neighbor was marked dead while another update
>> +	 * gave the lock up for a bit. Do not send such notifications.
>> +	 */
>
> I'd remove the comment, it's apparent from ->dead that there
> was a race and the rest is just repeating the condition bleow.

I figured it might be useful to clarify how it can come up, but yeah.
I'll respin without the comment.

> Otherwise looks good.
>
> Reviewed-by: Kuniyuki Iwashima <kuniyu@google.com>

Thanks!

      reply	other threads:[~2026-11-06 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 13:56 [PATCH net-next] net: neighbour: Avoid sending RTM_NEWNEIGH for a dead neighbor Petr Machata
2026-11-05 20:28 ` Kuniyuki Iwashima
2026-11-06 15:39   ` Petr Machata [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=87eccy2ckz.fsf@pmachata.org \
    --to=petrm@nvidia.com \
    --cc=aroulin@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.