netdev - Re: [PATCH v2] net/sched: sch_qfq: Fix race condition on qfq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aHAuLCWpBNC5hUwV@pop-os.localdomain>
Date: Thu, 10 Jul 2025 14:18:36 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Xiang Mei <xmei5@....edu>
Cc: Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
	gregkh@...uxfoundation.org, jhs@...atatu.com, jiri@...nulli.us,
	security@...nel.org
Subject: Re: [PATCH v2] net/sched: sch_qfq: Fix race condition on
 qfq_aggregate

On Wed, Jul 09, 2025 at 02:41:29PM -0700, Xiang Mei wrote:
> On Wed, Jul 09, 2025 at 01:19:20PM -0700, Jakub Kicinski wrote:
> > On Wed,  9 Jul 2025 11:06:22 -0700 Xiang Mei wrote:
> > > Reported-by: Xiang Mei <xmei5@....edu>
> > > Fixes: 462dbc9101ac ("pkt_sched: QFQ Plus: fair-queueing service at DRR cost")
> > > Signed-off-by: Xiang Mei <xmei5@....edu>
> > 
> > Reported-by is for cases where the bug is reported by someone else than
> 
> This bug's fixing is a little special since I am both the person who reported 
> it and the patch author. I may need a "Reported-by" tag mentioning me since I 
> exploited this bug in Google's bug bounty program (kerneCTF) and they will 
> verify the Reported-by tag to make sure I am the person found the bug.

Like others explained, "Reported-by" is for giving credits to the
reporter. Since you are both the author and reporter in this case, you already
have all the credits. They should understand this and credit you
properly. (Please do let us know if they don't, I am happy to help.)

Thanks for keeping updating your patch!