From: Simon Horman <horms@kernel.org>
To: zhangheng <zhangheng@kylinos.cn>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] net: korina: staging: octeon: Use DEV_STAT_INC()
Date: Mon, 11 Nov 2024 17:36:55 +0000 [thread overview]
Message-ID: <20241111173655.GG4507@kernel.org> (raw)
In-Reply-To: <20241109092024.4039494-1-zhangheng@kylinos.cn>
On Sat, Nov 09, 2024 at 05:20:24PM +0800, zhangheng wrote:
> syzbot/KCSAN reported that races happen when multiple CPUs updating
> dev->stats.tx_error concurrently. Adopt SMP safe DEV_STATS_INC() to
> update the dev->stats fields.
>
> Signed-off-by: zhangheng <zhangheng@kylinos.cn>
Hi,
I'm unsure what happened to the other 3 patches of the series
(and the cover letter?), but only this patch seems to be known
to lore.
This path looks like it is a fix for Networking, and thus should
be targeted at the net tree.
Subject: [PATCH net] ...
And, looking at git history, I think just "net: korina: " would be an
appropriate prefix for this patch. Along with a slightly more descriptive
subject. Maybe:
Subject: [PATCH net] net: korina: Use DEV_STAT_INC() to avoid race
Next, is there a stack trace available? If so, it would be nice
to include it, succinctly, in the patch description.
And if there there is a public syzbot/KCSAN report it would be nice
to include a link to it.
As for the changes, you mention that the patch fixes a race wrt to
tx_error. But the patch does more than that. Are the other changes also
strictly necessary? If so, I think that should be mentioned in the patch
description. And I'd suggest that any changes that are not strictly
necessary as a bug-fix should be handled via a follow-up patch targeted
at net-next.
As a fix there should be a Fixes tag immediately above your Signed-off-by
line (no blank line in between). It should cite the commit where the bug
was introduced, typically the first commit where it manifests for users.
Lastly, information on the process for Networking patches can be
found here: https://docs.kernel.org/process/maintainer-netdev.html
...
--
pw-bot: changes-requested
prev parent reply other threads:[~2024-11-11 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 9:20 [PATCH 3/4] net: korina: staging: octeon: Use DEV_STAT_INC() zhangheng
2024-11-11 17:36 ` Simon Horman [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=20241111173655.GG4507@kernel.org \
--to=horms@kernel.org \
--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=zhangheng@kylinos.cn \
/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).