From: Jiri Slaby <jirislaby@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kees Cook <keescook@chromium.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-serial@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-hardening@vger.kernel.org, llvm@lists.linux.dev,
patches@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH] tty: mxser: Remove __counted_by from mxser_board.ports[]
Date: Thu, 30 May 2024 08:22:03 +0200 [thread overview]
Message-ID: <d7c19866-6883-4f98-b178-a5ccf8726895@kernel.org> (raw)
In-Reply-To: <20240529-drop-counted-by-ports-mxser-board-v1-1-0ab217f4da6d@kernel.org>
On 29. 05. 24, 23:29, Nathan Chancellor wrote:
> Work for __counted_by on generic pointers in structures (not just
> flexible array members) has started landing in Clang 19 (current tip of
> tree). During the development of this feature, a restriction was added
> to __counted_by to prevent the flexible array member's element type from
> including a flexible array member itself such as:
>
> struct foo {
> int count;
> char buf[];
> };
>
> struct bar {
> int count;
> struct foo data[] __counted_by(count);
> };
>
> because the size of data cannot be calculated with the standard array
> size formula:
>
> sizeof(struct foo) * count
>
> This restriction was downgraded to a warning but due to CONFIG_WERROR,
> it can still break the build. The application of __counted_by on the
> ports member of 'struct mxser_board' triggers this restriction,
> resulting in:
>
> drivers/tty/mxser.c:291:2: error: 'counted_by' should not be applied to an array with element of unknown size because 'struct mxser_port' is a struct type with a flexible array member.
Huh -- what am I missing:
struct mxser_port {
struct tty_port port;
struct mxser_board *board;
unsigned long ioaddr;
unsigned long opmode_ioaddr;
u8 rx_high_water;
u8 rx_low_water;
int type; /* UART type */
u8 x_char; /* xon/xoff character */
u8 IER; /* Interrupt Enable Register */
u8 MCR; /* Modem control register */
u8 FCR; /* FIFO control register */
struct async_icount icount;
unsigned int timeout;
u8 read_status_mask;
u8 ignore_status_mask;
u8 xmit_fifo_size;
spinlock_t slock;
};
?
> This will be an error in a future compiler version [-Werror,-Wbounds-safety-counted-by-elt-type-unknown-size]
> 291 | struct mxser_port ports[] __counted_by(nports);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
> 1 error generated.
>
> Remove this use of __counted_by to fix the warning/error. However,
> rather than remove it altogether, leave it commented, as it may be
> possible to support this in future compiler releases.
This looks like a compiler bug/deficiency.
What does gcc say BTW?
> Cc: stable@vger.kernel.org
> Closes: https://github.com/ClangBuiltLinux/linux/issues/2026
> Fixes: f34907ecca71 ("mxser: Annotate struct mxser_board with __counted_by")
I would not say "Fixes" here. It only works around a broken compiler.
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
> ---
> drivers/tty/mxser.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/mxser.c b/drivers/tty/mxser.c
> index 458bb1280ebf..5b97e420a95f 100644
> --- a/drivers/tty/mxser.c
> +++ b/drivers/tty/mxser.c
> @@ -288,7 +288,7 @@ struct mxser_board {
> enum mxser_must_hwid must_hwid;
> speed_t max_baud;
>
> - struct mxser_port ports[] __counted_by(nports);
> + struct mxser_port ports[] /* __counted_by(nports) */;
> };
>
> static DECLARE_BITMAP(mxser_boards, MXSER_BOARDS);
thanks,
--
js
suse labs
next prev parent reply other threads:[~2024-05-30 6:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 21:29 [PATCH] tty: mxser: Remove __counted_by from mxser_board.ports[] Nathan Chancellor
2024-05-30 6:22 ` Jiri Slaby [this message]
2024-05-30 7:40 ` Greg Kroah-Hartman
2024-05-30 8:12 ` Gustavo A. R. Silva
2024-05-30 8:33 ` Jiri Slaby
2024-05-30 8:41 ` Jiri Slaby
2024-05-30 8:43 ` Bill Wendling
2024-05-30 8:46 ` Gustavo A. R. Silva
2024-06-03 6:07 ` Jiri Slaby
2024-06-03 8:26 ` Gustavo A. R. Silva
2024-06-12 20:04 ` Gustavo A. R. Silva
2024-05-30 8:42 ` Gustavo A. R. Silva
2024-05-30 17:43 ` Nathan Chancellor
2024-06-27 17:14 ` Kees Cook
2024-06-28 2:51 ` Gustavo A. R. Silva
2024-06-28 14:31 ` Greg Kroah-Hartman
2024-06-28 15:58 ` Kees Cook
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=d7c19866-6883-4f98-b178-a5ccf8726895@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=imx@lists.linux.dev \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=patches@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox