From: Thomas Gleixner <tglx@linutronix.de>
To: Z qiang <qiang.zhang1211@gmail.com>, paulmck@kernel.org
Cc: syzbot <syzbot+dce04ed6d1438ad69656@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] WARNING: suspicious RCU usage in __do_softirq
Date: Fri, 26 Apr 2024 19:23:04 +0200 [thread overview]
Message-ID: <8734r8t4w7.ffs@tglx> (raw)
In-Reply-To: <CALm+0cVvM56xse8ejf7+Wro+XBkFwY-MO1jyhWcVU8BWaZ2qjg@mail.gmail.com>
On Fri, Apr 26 2024 at 10:09, Z qiang wrote:
>> This looks quite nice to me, especially given that it avoids changing
>> all the other calls to __do_softirq(). Some architectures might want
>> to directly call handle_softirqs(), but if so, they can send the patches.
>
>
> Can you send an official patch? or I will send and add you to
> Co-developed-by tags.
Just send it along with a nice changelog and add:
Suggested-by: Thomas Gleixner <tglx@linutronix.de>
That's good enough.
prev parent reply other threads:[~2024-04-26 17:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 18:05 [syzbot] [kernel?] WARNING: suspicious RCU usage in __do_softirq syzbot
2024-04-16 7:05 ` syzbot
2024-04-16 8:10 ` Z qiang
2024-04-16 8:44 ` Z qiang
2024-04-17 1:13 ` Paul E. McKenney
2024-04-17 2:25 ` Z qiang
2024-04-17 22:39 ` Paul E. McKenney
2024-04-18 9:49 ` Z qiang
2024-04-18 22:49 ` Paul E. McKenney
2024-04-19 5:50 ` Z qiang
2024-04-19 6:11 ` Z qiang
2024-04-19 7:12 ` Paul E. McKenney
2024-04-19 7:29 ` Z qiang
2024-04-22 21:15 ` Thomas Gleixner
2024-04-23 2:20 ` Z qiang
2024-04-23 22:28 ` Paul E. McKenney
2024-04-26 2:09 ` Z qiang
2024-04-26 17:23 ` Thomas Gleixner [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=8734r8t4w7.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=qiang.zhang1211@gmail.com \
--cc=syzbot+dce04ed6d1438ad69656@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).