From: Jens Axboe <axboe@kernel.dk>
To: Cyber_black <Cyberblackk@proton.me>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "gabriel@krisman.be" <gabriel@krisman.be>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [BUG] io_uring: possible CQE32 overflow flush inconsistency in __io_cqring_overflow_flush()
Date: Sat, 20 Jun 2026 06:52:17 -0600 [thread overview]
Message-ID: <ccfe8e7e-f9cf-49e9-9c64-4a8754d16da6@kernel.dk> (raw)
In-Reply-To: <M9uVHmN1uFTdPdbQOITkChFjcJWO_U-BCOz4466zskh0n8rukyrE2nK4vlBcEQ8JBMyGZFPqBKCPyfZxYa0LdG5nkfxFBIcIOcSlAjrn1pU=@proton.me>
On 6/20/26 12:30 AM, Cyber_black wrote:
> Hi Greg,
>
> Thank you for your honest feedback. You are absolutely right that
> testing is essential.
>
> I was able to compile the kernel without issues, but I cannot test it
> properly at the moment due to lack of a suitable test environment (no
> KVM/QEMU setup, limited hardware resources, and financial
> constraints).
>
> If this means the report is considered invalid or cannot be accepted
> in its current form, please let me know clearly. I will revisit this
> when I have the appropriate infrastructure and resources to test it
> properly.
>
> I don't want to waste maintainers' time with untested patches. Thank
> you for your understanding.
Yes, please familiarize yourself with the process, just about everything
about your submission was wrong. Currently OOO, but I can take a look at
this when I get back next week.
--
Jens Axboe
next prev parent reply other threads:[~2026-06-20 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 6:30 Cyber_black
2026-06-20 12:52 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-20 13:31 Cyber_black
2026-06-20 6:13 Cyber_black
2026-06-20 6:17 ` gregkh
2026-06-19 8:05 Cyber_black
2026-06-19 16:07 ` Gabriel Krisman Bertazi
2026-06-19 4:49 Cyber_black
2026-06-19 6:00 ` Greg KH
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=ccfe8e7e-f9cf-49e9-9c64-4a8754d16da6@kernel.dk \
--to=axboe@kernel.dk \
--cc=Cyberblackk@proton.me \
--cc=gabriel@krisman.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®