From: Vladimir Oltean <olteanv@gmail.com>
To: Radoslaw Zielonek <radoslaw.zielonek@gmail.com>
Cc: vladimir.oltean@nxp.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com,
syzbot+a7d2b1d5d1af83035567@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, vinicius.gomes@intel.com,
willemdebruijn.kernel@gmail.com
Subject: Re: [syzbot] [net?] INFO: rcu detected stall in packet_release
Date: Wed, 29 May 2024 16:43:51 +0300 [thread overview]
Message-ID: <20240529134351.vtrh4oohb7g274ej@skbuf> (raw)
In-Reply-To: <20240528130331.21904-2-radoslaw.zielonek@gmail.com>
On Tue, May 28, 2024 at 03:03:25PM +0200, Radoslaw Zielonek wrote:
> Hello,
>
> Ah, sorry. I didn't notice that.
> The PoC has been tested by syzbot
> [https://syzkaller.appspot.com/bug?extid=c4c6c3dc10cc96bcf723]
>
> The full link:
> [https://lore.kernel.org/all/00000000000089427c0614c18cf4@google.com/T/]
>
> Radosław.
>
>
The patch, in the form you are presenting, obviously derails the phase
alignment of the new schedule when the core struggles to keep up with
the hrtimer. I am not in favor of adding any logic to taprio that
instructs it to behave out of spec.
next prev parent reply other threads:[~2024-05-29 13:43 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 [this message]
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
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=20240529134351.vtrh4oohb7g274ej@skbuf \
--to=olteanv@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radoslaw.zielonek@gmail.com \
--cc=syzbot+a7d2b1d5d1af83035567@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vinicius.gomes@intel.com \
--cc=vladimir.oltean@nxp.com \
--cc=willemdebruijn.kernel@gmail.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