From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Hillf Danton <hdanton@sina.com>
Cc: syzbot <syzbot+a7d2b1d5d1af83035567@syzkaller.appspotmail.com>,
edumazet@google.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, radoslaw.zielonek@gmail.com,
syzkaller-bugs@googlegroups.com, vinicius.gomes@intel.com
Subject: Re: [syzbot] [net?] INFO: rcu detected stall in packet_release
Date: Thu, 30 May 2024 03:33:25 +0300 [thread overview]
Message-ID: <20240530003325.h35jkwdm7mifcnc2@skbuf> (raw)
In-Reply-To: <20240529234745.3023-1-hdanton@sina.com>
On Thu, May 30, 2024 at 07:47:45AM +0800, Hillf Danton wrote:
> On Wed, 29 May 2024 16:10:02 -0700
> > syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> > INFO: rcu detected stall in sctp_addr_wq_timeout_handler
>
> Feel free to read again the root cause [1] Vlad.
>
> [1] https://lore.kernel.org/lkml/20240528122610.21393-2-radoslaw.zielonek@gmail.com/
>
> Adding the tested patch in the net tree now looks like a case of blind landing.
What is the fact that you submitted only my patch 1/2 for syzbot testing
supposed to prove? It is the second patch (2/2) that addresses what has
been reported here; I thought the tags made that clear:
https://lore.kernel.org/netdev/20240527153955.553333-2-vladimir.oltean@nxp.com/
Patch 2/2 has patch 1/2 as a dependency, which is why they were
submitted that way.
next prev parent reply other threads:[~2024-05-30 0:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 12:16 [syzbot] [net?] INFO: rcu detected stall in packet_release syzbot
2024-05-27 12:43 ` Eric Dumazet
2024-05-27 14:01 ` Vladimir Oltean
2024-05-28 12:25 ` Radoslaw Zielonek
2024-05-28 12:55 ` Vladimir Oltean
2024-05-28 13:03 ` Radoslaw Zielonek
2024-05-29 13:43 ` Vladimir Oltean
2024-05-29 22:52 ` Hillf Danton
2024-05-29 23:10 ` syzbot
2024-05-29 23:47 ` Hillf Danton
2024-05-30 0:33 ` Vladimir Oltean [this message]
2024-05-30 10:34 ` Hillf Danton
2024-05-30 11:19 ` syzbot
2024-05-30 11:57 ` Hillf Danton
2024-05-30 12:30 ` syzbot
2024-05-31 20:24 ` Hillf Danton
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=20240530003325.h35jkwdm7mifcnc2@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=radoslaw.zielonek@gmail.com \
--cc=syzbot+a7d2b1d5d1af83035567@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vinicius.gomes@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox