public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Jens Axboe <axboe@kernel.dk>, Qingyue Zhang <chunzhennn@qq.com>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
	Suoxing Zhang <aftern00n@qq.com>,
	cve@kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 1/2] io_uring/kbuf: fix signedness in this_len calculation
Date: Tue, 20 Jan 2026 23:11:05 +0530	[thread overview]
Message-ID: <5f33df40-9d18-4d0d-ba7d-60acef9e1d60@oracle.com> (raw)
In-Reply-To: <8c20196c-f208-464b-91cd-c87c22f83693@kernel.dk>

Hi Jens,


>> I see the Fixes tag documented is "Fixes: ae98dbf43d75
>> ("io_uring/kbuf: add support for incremental buffer consumption")"
>>
>> I think a more accurate Fixes tag is "Fixes: cf9536e550dd
>> ("io_uring/kbuf: enable bundles for incrementally consumed buffers")"
>> , Reason: Commit cf9536e550dd243a1681fdbf804221527da20a80 is the first
>> to move incremental-buffer accounting into the new helper
>> io_kbuf_inc_commit(), introducing this_len = min_t(int, len,
>> buf->len);. The signed int here is exactly what
>> c64eff368ac676e8540344d27a3de47e0ad90d21 corrects.
> 
> I took a look, and indeed, it is mis-tagged. The correct fixes tag
> should've been for cf9536e550dd.
> 

Thanks a lot for taking a look, will send a patch to vulns.git to get 
the CVE information corrected.

Regards,
Harshit


      reply	other threads:[~2026-01-20 17:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27 11:43 [PATCH 1/2] io_uring/kbuf: fix signedness in this_len calculation Qingyue Zhang
2025-08-27 14:40 ` Jens Axboe
2026-01-20 17:33 ` Harshit Mogalapalli
2026-01-20 17:38   ` Jens Axboe
2026-01-20 17:41     ` Harshit Mogalapalli [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=5f33df40-9d18-4d0d-ba7d-60acef9e1d60@oracle.com \
    --to=harshit.m.mogalapalli@oracle.com \
    --cc=aftern00n@qq.com \
    --cc=axboe@kernel.dk \
    --cc=chunzhennn@qq.com \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --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