From: Richard Henderson <richard.henderson@linaro.org>
To: "Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [qemu-web PATCH] contribute: define clear limits on bug report volume
Date: Fri, 25 Sep 2026 09:08:58 -0700 [thread overview]
Message-ID: <a6cfb8ee-ce2e-408b-bc70-e85e8db7ed38@linaro.org> (raw)
In-Reply-To: <98a4b3e6-e538-4bd2-8cad-7307ce24b698@redhat.com>
Good idea, Daniel. While you're fixing typos, Thomas:
On 9/25/26 00:51, Thomas Huth wrote:
> On 24/09/2026 15.56, Daniel P. Berrangé wrote:
>> Recently QEMU has received a denial of service attack on
>> its bug tracker in the form of 120 reports in 10 minutes,
>> and now repeated by another reporter in the form of 50
>> reports in the same day.
>>
>> Prior to switching security disclosures to the bug tracker,
>> single reporters have submited 18, 22, and 114 bug reports.
submitted.
>>
>> None of this is sustainable. It is an effective denial of
>> service attack on the project maintainers' time. Every bug
>> report is a TODO item added to someone's workload.
>>
>> It is time to put hard limits on how many bugs, discovered
>> with assitance of automated tools, we are willing to accept
assistance
>> in a givenm time frame.
given
r~
next prev parent reply other threads:[~2026-09-25 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:56 [qemu-web PATCH] contribute: define clear limits on bug report volume Daniel P. Berrangé
2026-09-24 15:12 ` Alex Bennée
2026-09-24 15:29 ` Daniel P. Berrangé
2026-10-02 11:12 ` Markus Armbruster
2026-09-25 7:51 ` Thomas Huth
2026-09-25 16:08 ` Richard Henderson [this message]
2026-09-30 8:57 ` Thomas Huth
2026-10-02 10:46 ` Markus Armbruster
2026-10-02 10:57 ` Mark Cave-Ayland
2026-10-02 11:20 ` Markus Armbruster
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=a6cfb8ee-ce2e-408b-bc70-e85e8db7ed38@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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 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.