spi: Don't use flexible array in struct spi_message definition
PATCH 1/1 spi: Don't use flexible array in struct spi_message definition
The struct spi_message can be embedded into another structures. With that the flexible array might be problematic as sparse complains about it, although there is no real issue in the code because when the message is embedded it doesn't use flexible array member. That memeber is a private to spi_message_alloc() API, so move it to that API in a form of an inherited data type.
--- include/linux/spi/spi.h | 27 +++++++++++++-------------- 1 file changed, 13 insertions(+), 14 deletions(-)
include/linux/spi/spi.h +13 -14
@@ -1086,8 +1086,6 @@ struct spi_transfer {* @state: for use by whichever driver currently owns the message * @resources: for resource management when the SPI message is processed * @prepared: spi_prepare_message was called for the this message -* @t: for use with spi_message_alloc() when message and transfers have -* been allocated together * * A @spi_message is used to execute an atomic sequence of data transfers, * each represented by a struct spi_transfer. The sequence is "atomic"
@@ -1142,9 +1140,6 @@ struct spi_message {/* List of spi_res resources when the SPI message is processed */ struct list_head resources; - -/* For embedding transfers into the memory of the message */ -struct spi_transfer t[]; };static inline void spi_message_init_no_memset (struct spi_message *m)
@@ -1203,17 +1198,21 @@ struct spi_transfer *xfers, unsigned int num_xfers)*/ static inline struct spi_message *spi_message_alloc (unsigned ntrans,gfp_t flags) { -struct spi_message *m; +struct spi_message_with_transfers { +struct spi_message m; +struct spi_transfer t[]; + } *mwt; +unsigned i; - m =kzalloc (struct_size (m, t, ntrans), flags); -if (m) { -unsigned i; + mwt =kzalloc (struct_size (mwt, t, ntrans), flags); +if (!mwt) +return NULL ; -spi_message_init_no_memset (m); -for (i =0 ; i < ntrans; i++) -spi_message_add_tail (&m->t[i], m); - } -return m; +spi_message_init_no_memset (&mwt->m); +for (i =0 ; i < ntrans; i++) +spi_message_add_tail (&mwt->t[i], &mwt->m); + +return &mwt->m; }static inline void spi_message_free (struct spi_message *m)
Signature · 1 line
2.40.0.1.gaa8946217a0b
Quoted 11 lines · Andy Shevchenko
The struct
spi_messagecan be embedded into another structures. With that the flexible array might be problematic as sparse complains about it, although there is no real issue in the code because when the message is embedded it doesn't use flexible array member. That memeber is a private tospi_message_alloc()API, so move it to that API in a form of an inherited data type.Reported-by Marc Kleine-Budde <[email protected]>Fixes 75e308ffc4f0 ("spi: Use struct_size() helper"))Signed-off-by Andy Shevchenko <[email protected]>
Thank you for the timely fix!
regards,
Marc
Signature · 4 lines
Pengutronix e.K. | Marc Kleine-Budde | Embedded Linux | https://www.pengutronix.de | Vertretung Nürnberg | Phone: +49-5121-206917-129 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
Mark Brown
maintainerQuoted 8 lines · Andy Shevchenko
The struct
spi_messagecan be embedded into another structures. With that the flexible array might be problematic as sparse complains about it, although there is no real issue in the code because when the message is embedded it doesn't use flexible array member. That memeber is a private tospi_message_alloc()API, so move it to that API in a form of an inherited data type.[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: Don't use flexible array in struct spi_message definition
commit: f6d7f050e258e3c71e310f5167c4d65bbefaeb31
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark