public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Dmitry Antipov <dmantipov@yandex•ru>
Cc: kuba@kernel•org, l.stelmach@samsung•com, netdev@vger•kernel.org
Subject: Re: [PATCH] [v2] net: asix: fix fortify warning
Date: Tue, 12 Dec 2023 22:10:23 +0000	[thread overview]
Message-ID: <170241902385.2523.3221472990711527162.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231211090535.9730-1-dmantipov@yandex.ru>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:

On Mon, 11 Dec 2023 12:05:32 +0300 you wrote:
> When compiling with gcc version 14.0.0 20231129 (experimental) and
> CONFIG_FORTIFY_SOURCE=y, I've noticed the following warning:
> 
> ...
> In function 'fortify_memcpy_chk',
>     inlined from 'ax88796c_tx_fixup' at drivers/net/ethernet/asix/ax88796c_main.c:287:2:
> ./include/linux/fortify-string.h:588:25: warning: call to '__read_overflow2_field'
> declared with attribute warning: detected read beyond size of field (2nd parameter);
> maybe use struct_group()? [-Wattribute-warning]
>   588 |                         __read_overflow2_field(q_size_field, size);
>       |                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ...
> 
> [...]

Here is the summary with links:
  - [v2] net: asix: fix fortify warning
    https://git.kernel.org/netdev/net-next/c/2a6264480020

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-12-12 22:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 13:38 [PATCH] net: asix: fix fortify warning Dmitry Antipov
2023-12-09  0:07 ` Jakub Kicinski
2023-12-11  9:05   ` [PATCH] [v2] " Dmitry Antipov
2023-12-12  9:33     ` Lukasz Stelmach
2023-12-12 22:10     ` patchwork-bot+netdevbpf [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=170241902385.2523.3221472990711527162.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=dmantipov@yandex$(echo .)ru \
    --cc=kuba@kernel$(echo .)org \
    --cc=l.stelmach@samsung$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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