From: Arnd Bergmann <arnd@xxxxxxxx>
Date: Wed, 23 Aug 2017 15:59:49 +0200
> gcc-8.0.0 (snapshot) points out that we copy a variable-length string
> into a fixed length field using memcpy() with the destination length,
> and that ends up copying whatever follows the string:
>
> inlined from 'ql_core_dump' at drivers/net/ethernet/qlogic/qlge/qlge_dbg.c:1106:2:
> drivers/net/ethernet/qlogic/qlge/qlge_dbg.c:708:2: error: 'memcpy' reading 15 bytes from a region of size 14 [-Werror=stringop-overflow=]
> memcpy(seg_hdr->description, desc, (sizeof(seg_hdr->description)) - 1);
>
> Changing it to use strncpy() will instead zero-pad the destination,
> which seems to be the right thing to do here.
>
> The bug is probably harmless, but it seems like a good idea to address
> it in stable kernels as well, if only for the purpose of building with
> gcc-8 without warnings.
>
> Cc: stable@xxxxxxxxxxxxxxx
Please don't use explicit stable CC:'ing for networking changes.
> Fixes: a61f80261306 ("qlge: Add ethtool register dump function.")
> Signed-off-by: Arnd Bergmann <arnd@xxxxxxxx>
Applied to 'net' and queued up for -stable, thanks.