All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Juhee Kang <claudiajkang@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Kurt Kanzenbach <kurt@linutronix.de>
Subject: [PATCH net 0/5] hsr: HSR send/recv fixes
Date: Wed, 16 Nov 2022 17:59:38 +0100	[thread overview]
Message-ID: <20221116165943.1776754-1-bigeasy@linutronix.de> (raw)

I started playing with HSR and run into a problem. Tested latest
upstream -rc and noticed more problems. Now it appears to work.
For testing I have a small three node setup with iperf and ping. While
iperf doesn't complain ping reports missing packets and duplicates.

One thing I didn't mention in the patches (and remember now) is that
before the revert (while looking for the reason of the duplicated
packets) I randomly observed a crash while hsr network was up but had no
traffic. It didn't happen with traffic or I was not patience enough.
It appears from the backtrace that the node was removed twice. This was
the additional boost for the revert since it appears it is not used. I
Didn't see the crash after the revert.

Sebastian



             reply	other threads:[~2022-11-16 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 16:59 Sebastian Andrzej Siewior [this message]
2022-11-16 16:59 ` [PATCH net 1/5] Revert "net: hsr: use hlist_head instead of list_head for mac addresses" Sebastian Andrzej Siewior
2022-11-16 16:59 ` [PATCH net 2/5] hsr: Add a rcu-read lock to hsr_forward_skb() Sebastian Andrzej Siewior
2022-11-16 16:59 ` [PATCH net 3/5] hsr: Disable netpoll Sebastian Andrzej Siewior
2022-11-16 16:59 ` [PATCH net 4/5] hsr: Synchronize sending frames to have always incremented outgoing seq nr Sebastian Andrzej Siewior
2022-11-16 16:59 ` [PATCH net 5/5] hsr: Synchronize sequence number updates Sebastian Andrzej Siewior
2022-11-17 16:47   ` kernel test robot

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=20221116165943.1776754-1-bigeasy@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=claudiajkang@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kurt@linutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tglx@linutronix.de \
    /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.