public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Qingyue Zhang <chunzhennn@qq.com>
Cc: aftern00n@qq.com, io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] io_uring/kbuf: fix infinite loop in io_kbuf_inc_commit()
Date: Thu, 28 Aug 2025 05:50:01 -0600	[thread overview]
Message-ID: <3aba1ff4-4e8b-4f34-b300-5e7aeb18ec15@kernel.dk> (raw)
In-Reply-To: <tencent_2DDD243AE6E04DB6288696AC252D1B46EF06@qq.com>

On 8/27/25 9:27 PM, Qingyue Zhang wrote:
> Thanks for taking care of this report!
> 
> Regarding tags, it would be nice to add a 
> 'Reported-by: Suoxing Zhang <aftern00n@qq.com>'
> tag too, as this report and reproducer are
> developed by both of us.

Done!

> And absolutely, please feel free to use our 
> reproducer for a test case! I'm glad it can 
> be useful. Your version with idiomatic 
> liburing looks great.

Perfect, will do.

> This is my first contribution to the Linux 
> Kernel, and I really appreciate your patience 
> and quick responses throughout this process!

Let's hope it's the first of many!

-- 
Jens Axboe

      reply	other threads:[~2025-08-28 11:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250827114339.367080-1-chunzhennn@qq.com>
2025-08-27 11:44 ` [PATCH 2/2] io_uring/kbuf: fix infinite loop in io_kbuf_inc_commit() Qingyue Zhang
2025-08-27 14:30   ` Jens Axboe
2025-08-27 21:45     ` Jens Axboe
2025-08-27 21:59       ` Keith Busch
2025-08-27 22:23         ` Jens Axboe
2025-08-28  1:36       ` Qingyue Zhang
2025-08-28  2:08         ` Jens Axboe
2025-08-28  2:49           ` Qingyue Zhang
2025-08-28  2:50             ` Jens Axboe
2025-08-28  2:58               ` Jens Axboe
2025-08-28  3:27                 ` Qingyue Zhang
2025-08-28 11:50                   ` Jens Axboe [this message]

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=3aba1ff4-4e8b-4f34-b300-5e7aeb18ec15@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=aftern00n@qq.com \
    --cc=chunzhennn@qq.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@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