From: Kees Cook <keescook@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jens Axboe <axboe@kernel.dk>,
Pavel Begunkov <asml.silence@gmail.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
stable@vger.kernel.org, io-uring@vger.kernel.org,
Dylan Yudaken <dylany@fb.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] io_uring: Replace 0-length array with flexible array
Date: Thu, 5 Jan 2023 10:04:19 -0800 [thread overview]
Message-ID: <202301051003.27CF3DC@keescook> (raw)
In-Reply-To: <Y7Z+xN+BDy5yoK5f@kroah.com>
On Thu, Jan 05, 2023 at 08:39:48AM +0100, Greg KH wrote:
> On Wed, Jan 04, 2023 at 07:37:48PM -0800, Kees Cook wrote:
> > Zero-length arrays are deprecated[1]. Replace struct io_uring_buf_ring's
> > "bufs" with a flexible array member. (How is the size of this array
> > verified?) Detected with GCC 13, using -fstrict-flex-arrays=3:
> >
> > In function 'io_ring_buffer_select',
> > inlined from 'io_buffer_select' at io_uring/kbuf.c:183:10:
> > io_uring/kbuf.c:141:23: warning: array subscript 255 is outside the bounds of an interior zero-length array 'struct io_uring_buf[0]' [-Wzero-length-bounds]
> > 141 | buf = &br->bufs[head];
> > | ^~~~~~~~~~~~~~~
> > In file included from include/linux/io_uring.h:7,
> > from io_uring/kbuf.c:10:
> > include/uapi/linux/io_uring.h: In function 'io_buffer_select':
> > include/uapi/linux/io_uring.h:628:41: note: while referencing 'bufs'
> > 628 | struct io_uring_buf bufs[0];
> > | ^~~~
> >
> > [1] https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays
> >
> > Fixes: c7fb19428d67 ("io_uring: add support for ring mapped supplied buffers")
> > Cc: Jens Axboe <axboe@kernel.dk>
> > Cc: Pavel Begunkov <asml.silence@gmail.com>
> > Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>
> > Cc: stable@vger.kernel.org
>
> Build problem aside, why is this a stable kernel issue?
My thinking was that since this is technically a UAPI change, it'd be
best to get it changed as widely as possible.
--
Kees Cook
next prev parent reply other threads:[~2023-01-05 18:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 3:37 [PATCH] io_uring: Replace 0-length array with flexible array Kees Cook
2023-01-05 4:33 ` Kees Cook
2023-01-05 5:58 ` kernel test robot
2023-01-05 7:39 ` Greg KH
2023-01-05 18:04 ` Kees Cook [this message]
2023-01-05 19:38 ` Greg KH
2023-01-05 20:01 ` Kees Cook
2023-01-05 10:52 ` kernel test robot
2023-01-05 12:23 ` kernel test robot
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=202301051003.27CF3DC@keescook \
--to=keescook@chromium.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=dylany@fb.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.