From: Simon Horman <horms@kernel.org>
To: Dharanitharan R <dharanitharan725@gmail.com>
Cc: syzbot+422806e5f4cce722a71f@syzkaller.appspotmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] team: fix qom_list corruption by using list_del_init_rcu()
Date: Mon, 8 Dec 2025 17:33:55 +0000 [thread overview]
Message-ID: <aTcMA29O_JC5Npdg@horms.kernel.org> (raw)
In-Reply-To: <20251207025807.1674-2-dharanitharan725@gmail.com>
On Sun, Dec 07, 2025 at 02:58:08AM +0000, Dharanitharan R wrote:
> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> Reported-by: syzbot+422806e5f4cce722a71f@syzkaller.appspotmail.com
> Signed-off-by: Dharanitharan R <dharanitharan725@gmail.com>
Hi Dharanitharan,
Please slow down!
It is not appropriate to send multiple versions of a patch CCed to
netdev within in quick succession. Rather, 24h should elapse between
versions. And moreover, I'd advise against CCing netdev on patches
targeted at syzbot testing.
When you do post a fix, for a problem flagged by syzbot, to netdev please
include:
* A description of the problem, and
* How the approach taken fixes it
Typically such a patch will be a bug fix for code present in the net tree.
So it should be targeted at the net tree like this:
Subject: [PATCH net] ...
And it should probably include the following tags:
Fixes:
Reported-by:
Closes:
Especially the Fixes tag.
For an example please see:
https://lore.kernel.org/netdev/20251122002027.695151-1-zlatistiv@gmail.com/
For more information on the Netdev development process please see:
https://docs.kernel.org/process/maintainer-netdev.html
Thanks.
--
pw-bot: changes-requested
next prev parent reply other threads:[~2025-12-08 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 22:14 [syzbot] [net?] BUG: corrupted list in team_priority_option_set (6) syzbot
2025-12-07 2:58 ` [PATCH] team: fix qom_list corruption by using list_del_init_rcu() Dharanitharan R
2025-12-07 2:59 ` syzbot
2025-12-08 17:33 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-06 18:25 Dharanitharan R
2025-12-06 18:34 Dharanitharan R
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=aTcMA29O_JC5Npdg@horms.kernel.org \
--to=horms@kernel.org \
--cc=dharanitharan725@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+422806e5f4cce722a71f@syzkaller.appspotmail.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 NNTP newsgroup(s).