From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: Fwd: RCU stalls with wireguard over bonding over igb on Linux 6.3.0+
Date: Mon, 3 Jul 2023 04:09:42 +0200 [thread overview]
Message-ID: <ZKIt5vyc_HunicuZ@zx2c4.com> (raw)
In-Reply-To: <ZKIlibX5wCgWlonq@debian.me>
On Mon, Jul 03, 2023 at 08:34:01AM +0700, Bagas Sanjaya wrote:
> On Sun, Jul 02, 2023 at 03:46:38PM +0200, Jason A. Donenfeld wrote:
> > I've got an overdue patch that I still need to submit to netdev, which
> > I suspect might actually fix this.
> >
> > Can you let me know if
> > https://git.zx2c4.com/wireguard-linux/patch/?id=54d5e4329efe0d1dba8b4a58720d29493926bed0
> > solves the problem?
>
> The reporter on Bugzilla [1] said it fixed the regression, so telling
> regzbot:
>
> #regzbot fix: 54d5e4329efe0d
That's not correct. I tend to send patches to netdev@, not pulls, so the
commit is going to be different. Just leave this alone for a bit and
tidy things up once everything hits the main trees.
next prev parent reply other threads:[~2023-07-03 2:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 3:31 Fwd: RCU stalls with wireguard over bonding over igb on Linux 6.3.0+ Bagas Sanjaya
2023-07-02 11:57 ` Bagas Sanjaya
2023-07-02 12:37 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-02 13:46 ` Jason A. Donenfeld
2023-07-03 1:29 ` Jason A. Donenfeld
2023-07-03 1:34 ` Bagas Sanjaya
2023-07-03 2:09 ` Jason A. Donenfeld [this message]
2023-07-03 5:18 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-03 11:52 ` Jason A. Donenfeld
2023-07-04 10:08 ` Bagas Sanjaya
2023-07-02 14:03 ` Sam James
2023-07-02 14:03 ` Sam James
2023-07-02 14:08 ` Bagas Sanjaya
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=ZKIt5vyc_HunicuZ@zx2c4.com \
--to=jason@zx2c4.com \
--cc=bagasdotme@gmail.com \
--cc=regressions@lists.linux.dev \
/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.