public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lai, Yi" <yi1.lai@linux.intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
	asml.silence@gmail.com, linux-kernel@vger.kernel.org,
	io-uring@vger.kernel.org, cgroups@vger.kernel.org,
	dqminh@cloudflare.com, longman@redhat.com,
	adriaan.schmidt@siemens.com, florian.bezdeka@siemens.com,
	stable@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	pengfei.xu@intel.com, yi1.lai@intel.com
Subject: Re: [PATCH 1/1] io_uring/sqpoll: do not allow pinning outside of cpuset
Date: Wed, 18 Sep 2024 14:21:25 +0800	[thread overview]
Message-ID: <ZupxZeILxuKqFsRq@ly-workstation> (raw)
In-Reply-To: <5237b4c0-973f-44cc-a6ee-08302871fd19@kernel.dk>

Thanks for reply. I will include lkp into search database before sending
out fuzzing findings.

Regards,
Yi Lai

On Wed, Sep 18, 2024 at 12:16:41AM -0600, Jens Axboe wrote:
> On 9/17/24 9:56 PM, Lai, Yi wrote:
> > Hi Felix Moessbauer,
> > 
> > Greetings!
> > 
> > I used Syzkaller and found that there is KASAN: use-after-free Read in io_sq_offload_create in Linux-next tree - next-20240916.
> > 
> > After bisection and the first bad commit is:
> > "
> > f011c9cf04c0 io_uring/sqpoll: do not allow pinning outside of cpuset
> > "
> 
> This is known and fixed:
> 
> https://git.kernel.dk/cgit/linux/commit/?h=for-6.12/io_uring&id=a09c17240bdf2e9fa6d0591afa9448b59785f7d4
> 
> -- 
> Jens Axboe

      reply	other threads:[~2024-09-18  6:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 15:00 [PATCH 1/1] io_uring/sqpoll: do not allow pinning outside of cpuset Felix Moessbauer
2024-09-09 15:08 ` Jens Axboe
2024-09-09 15:09 ` Jens Axboe
2024-09-18  3:56 ` Lai, Yi
2024-09-18  6:16   ` Jens Axboe
2024-09-18  6:21     ` Lai, Yi [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=ZupxZeILxuKqFsRq@ly-workstation \
    --to=yi1.lai@linux.intel.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=dqminh@cloudflare.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=pengfei.xu@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yi1.lai@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox