From: Jens Axboe <axboe@kernel.dk>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"oliver.sang@intel.com" <oliver.sang@intel.com>
Cc: "oe-lkp@lists.linux.dev" <oe-lkp@lists.linux.dev>,
"lkp@intel.com" <lkp@intel.com>,
"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>
Subject: Re: [axboe-block:for-6.12/io_uring] [io_uring/sqpoll] f011c9cf04: BUG:KASAN:slab-out-of-bounds_in_io_sq_offload_create
Date: Mon, 16 Sep 2024 03:10:58 -0600 [thread overview]
Message-ID: <da3f34b8-220c-4951-835e-a9036e79f47f@kernel.dk> (raw)
In-Reply-To: <1c5f77a9253ac3a56a1e00f7b588d86d447a54c5.camel@siemens.com>
On 9/16/24 3:09 AM, MOESSBAUER, Felix wrote:
> Thanks for fixing. While we are at it, I noticed that putting the
> cpumask on the stack is discouraged. We should better allocate it like
> in my other patches. Shall I send a fixup patch?
Yes probably not a bad idea, some systems configure with a large number
of possible CPUs.
--
Jens Axboe
prev parent reply other threads:[~2024-09-16 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 8:35 [axboe-block:for-6.12/io_uring] [io_uring/sqpoll] f011c9cf04: BUG:KASAN:slab-out-of-bounds_in_io_sq_offload_create kerne test robot
2024-09-16 9:03 ` Jens Axboe
2024-09-16 9:09 ` MOESSBAUER, Felix
2024-09-16 9:10 ` 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=da3f34b8-220c-4951-835e-a9036e79f47f@kernel.dk \
--to=axboe@kernel.dk \
--cc=felix.moessbauer@siemens.com \
--cc=io-uring@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@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