All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Xiang Mei <xmei5@asu.edu>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
	netdev@vger.kernel.org, gregkh@linuxfoundation.org,
	jhs@mojatatu.com, jiri@resnulli.us, security@kernel.org
Subject: Re: [PATCH v1] net/sched: sch_qfq: Fix race condition on qfq_aggregate
Date: Tue, 8 Jul 2025 05:18:18 +0200	[thread overview]
Message-ID: <20250708031818.GA4539@1wt.eu> (raw)
In-Reply-To: <aGxgzS2dZo8fKUw5@xps>

On Mon, Jul 07, 2025 at 05:05:33PM -0700, Xiang Mei wrote:
> I have two more questions:
> 
> 1) Is the patch provider the person who usually adds the "Reported-by" tag?

Yes, usually when one person authors a patch to fix a problem reported
by someone else, a Reported-by tag is added to credit that reporter.
When it's the same person as the one who authors the patch, it's not
needed.

> 2) Am I allowed to request a CVE number for this race condition bug?

No, this will happen automatically once the fix is considered for
backporting by the stable team, and the cve team decides which fixes
need a CVE. The process is described here: Documentation/process/cve.rst.

Regards,
Willy

  reply	other threads:[~2025-07-08  3:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPpSM+SKOj9U8g_QsGp8M45dtEwvX4B_xdd7C0mP9pYu1b4mzA@mail.gmail.com>
2025-06-29 14:28 ` sch_qfq: race conditon on qfq_aggregate (net/sched/sch_qfq.c) Jamal Hadi Salim
2025-06-30  3:11   ` Xiang Mei
2025-06-30 11:36     ` Jamal Hadi Salim
2025-06-30 18:49       ` Xiang Mei
2025-06-30 23:09         ` Cong Wang
2025-07-01  2:52           ` Xiang Mei
2025-07-02 19:41           ` Xiang Mei
2025-07-04  4:55             ` Cong Wang
2025-07-05 22:39               ` [PATCH v1] net/sched: sch_qfq: Fix race condition on qfq_aggregate Xiang Mei
2025-07-05 22:49                 ` Xiang Mei
2025-07-07 18:05                   ` Cong Wang
2025-07-07 17:58                 ` Jakub Kicinski
2025-07-07 23:42                   ` Xiang Mei
2025-07-08  0:20                     ` Jakub Kicinski
2025-07-07 18:03                 ` Cong Wang
2025-07-08  0:05                   ` Xiang Mei
2025-07-08  3:18                     ` Willy Tarreau [this message]
2025-07-09 18:08                       ` Xiang Mei
2025-07-09 18:06                   ` [PATCH v2] " Xiang Mei
2025-07-09 20:19                     ` Jakub Kicinski
2025-07-09 21:41                       ` Xiang Mei
2025-07-09 21:54                         ` Jakub Kicinski
2025-07-10 10:06                           ` Xiang Mei
2025-07-10 21:18                         ` Cong Wang
2025-07-10 22:45                           ` Xiang Mei
2025-07-01 14:02         ` sch_qfq: race conditon on qfq_aggregate (net/sched/sch_qfq.c) Jamal Hadi Salim

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=20250708031818.GA4539@1wt.eu \
    --to=w@1wt.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=security@kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    --cc=xmei5@asu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.