From: Richard Weinberger <richard@nod.at>
To: Kees Cook <kees@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
anton ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
Jens Axboe <axboe@kernel.dk>, Hannes Reinecke <hare@suse.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Tiwei Bie <tiwei.btw@antgroup.com>,
linux-um <linux-um@lists.infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-hardening <linux-hardening@vger.kernel.org>
Subject: Re: [PATCH] ubd: Use pointer-to-pointers for io_thread_req arrays
Date: Mon, 23 Feb 2026 22:52:54 +0100 (CET) [thread overview]
Message-ID: <905832921.1560.1771883574809.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20260223214341.work.846-kees@kernel.org>
----- Ursprüngliche Mail -----
> Von: "Kees Cook" <kees@kernel.org>
> An: "richard" <richard@nod.at>
> CC: "Kees Cook" <kees@kernel.org>, "Nathan Chancellor" <nathan@kernel.org>, "Guenter Roeck" <linux@roeck-us.net>, "anton
> ivanov" <anton.ivanov@cambridgegreys.com>, "Johannes Berg" <johannes@sipsolutions.net>, "Jens Axboe" <axboe@kernel.dk>,
> "Hannes Reinecke" <hare@suse.de>, "Martin K. Petersen" <martin.petersen@oracle.com>, "Tiwei Bie"
> <tiwei.btw@antgroup.com>, "linux-um" <linux-um@lists.infradead.org>, "Al Viro" <viro@zeniv.linux.org.uk>,
> "linux-kernel" <linux-kernel@vger.kernel.org>, "linux-hardening" <linux-hardening@vger.kernel.org>
> Gesendet: Montag, 23. Februar 2026 22:43:45
> Betreff: [PATCH] ubd: Use pointer-to-pointers for io_thread_req arrays
> Having an unbounded array for irq_req_buffer and io_req_buffer doesn't
> provide any bounds safety, and confuses the needed allocation type,
> which is returning a pointer to pointers. Instead of the implicit cast,
> switch the variable types.
>
> Reported-by: Nathan Chancellor <nathan@kernel.org>
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Closes:
> https://lore.kernel.org/all/b04b6c13-7d0e-4a89-9e68-b572b6c686ac@roeck-us.net
> Fixes: 69050f8d6d07 ("treewide: Replace kmalloc with kmalloc_obj for non-scalar
> types")
> Signed-off-by: Kees Cook <kees@kernel.org>
> ---
> Cc: Richard Weinberger <richard@nod.at>
> Cc: Anton Ivanov <anton.ivanov@cambridgegreys.com>
> Cc: Johannes Berg <johannes@sipsolutions.net>
> Cc: Jens Axboe <axboe@kernel.dk>
> Cc: Hannes Reinecke <hare@suse.de>
> Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
> Cc: Tiwei Bie <tiwei.btw@antgroup.com>
> Cc: <linux-um@lists.infradead.org>
> ---
> arch/um/drivers/ubd_kern.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
Acked-by: Richard Weinberger <richard@nod.at>
Thanks,
//richard
prev parent reply other threads:[~2026-02-23 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 21:43 [PATCH] ubd: Use pointer-to-pointers for io_thread_req arrays Kees Cook
2026-02-23 21:52 ` Richard Weinberger [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=905832921.1560.1771883574809.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=anton.ivanov@cambridgegreys.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=johannes@sipsolutions.net \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=martin.petersen@oracle.com \
--cc=nathan@kernel.org \
--cc=tiwei.btw@antgroup.com \
--cc=viro@zeniv.linux.org.uk \
/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