From: Jakub Kicinski <kuba@kernel.org>
To: Yuan Tan <yuantan098@gmail.com>
Cc: Ren Wei <n05ec@lzu.edu.cn>,
netdev@vger.kernel.org, jhs@mojatatu.com, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, peilin.ye@bytedance.com,
cong.wang@bytedance.com, gnault@redhat.com, yifanwucs@gmail.com,
tomapufckgml@gmail.com, zcliangcn@gmail.com, bird@lzu.edu.cn,
bronzed_45_vested@icloud.com
Subject: Re: [PATCH net 1/2] net/sched: act_skbmod: require an Ethernet header for MAC rewrites
Date: Tue, 21 Jul 2026 18:22:45 -0700 [thread overview]
Message-ID: <20260721182245.50059a0d@kernel.org> (raw)
In-Reply-To: <CAPuPA7KMdDSGKWJXEZzSpgbdUj4_BGGX2+CedgchoD77bPd8sg@mail.gmail.com>
On Tue, 30 Jun 2026 23:46:46 -0700 Yuan Tan wrote:
> On Tue, Jun 30, 2026 at 5:20 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > On Tue, 30 Jun 2026 17:10:16 -0700 Jakub Kicinski wrote:
> > > On Mon, 29 Jun 2026 10:46:03 +0800 Ren Wei wrote:
> > > Let's do away with the 5 reported-by tags? You can use a tag for your
> > > tool or your team, it doesn't have to be a person. Look at sashiko or
> > > syzbot reported-by tags.
> >
> > On second thought, if y'all work together maybe there should be no
> > reported-by tag at all? Can you explain the situation?
>
> Hi Jakub,
>
> Since February, our team's bug-finding tool has found hundreds of bugs
> and vulnerabilities. Several people have helped improve the tool to
> discover more bugs, and verify that they are real. I did not want
> their credit to be lost, so I added Reported-by tags based on whether
> they contributed to finding a particular bug.
>
> I agree, though, that having five Reported-by tags may not look ideal.
> Maybe using the tool name instead would be better. I will discuss this
> with the others.
>
> We also found many external volunteers to submit patches, instead of
> simply dumping bug reports on the community and leaving it at that. We
> were worried that too many reports might annoy maintainers. That said,
> it may be easier in some cases for maintainers to fix the issues
> themselves rather than review our patches, since we are not experts in
> every subsystem.
Sorry, I was AFK for the last 2.5 weeks.
I expect you to make the changes I asked for.
There are multiple teams doing the same thing as you are,
and nobody else has so many tags.
next prev parent reply other threads:[~2026-07-22 1:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1782548651.git.bronzed_45_vested@icloud.com>
2026-06-29 2:46 ` [PATCH net 1/2] net/sched: act_skbmod: require an Ethernet header for MAC rewrites Ren Wei
2026-07-01 0:10 ` Jakub Kicinski
2026-07-01 0:20 ` Jakub Kicinski
2026-07-01 6:46 ` Yuan Tan
2026-07-22 1:22 ` Jakub Kicinski [this message]
2026-07-22 17:16 ` Yuan Tan
2026-06-29 2:46 ` [PATCH net 2/2] net/sched: act_vlan: skip pop_eth on non-Ethernet devices Ren Wei
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=20260721182245.50059a0d@kernel.org \
--to=kuba@kernel.org \
--cc=bird@lzu.edu.cn \
--cc=bronzed_45_vested@icloud.com \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=n05ec@lzu.edu.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peilin.ye@bytedance.com \
--cc=tomapufckgml@gmail.com \
--cc=yifanwucs@gmail.com \
--cc=yuantan098@gmail.com \
--cc=zcliangcn@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