All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kees Cook <keescook@chromium.org>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, axboe@kernel.dk, asml.silence@gmail.com,
	dsahern@kernel.org, dylany@fb.com, yajun.deng@linux.dev,
	petrm@nvidia.com, liuhangbin@gmail.com, leon@kernel.org,
	syzkaller@googlegroups.com, willemb@google.com,
	pablo@netfilter.org, netdev@vger.kernel.org, nathan@kernel.org,
	ndesaulniers@google.com, trix@redhat.com,
	alibuda@linux.alibaba.com, jk@codeconstruct.com.au,
	bigeasy@linutronix.de, imagedong@tencent.com, kuniyu@amazon.com,
	liu3101@purdue.edu, wsa+renesas@sang-engineering.com,
	william.xuanziyang@huawei.com, linux-kernel@vger.kernel.org,
	llvm@lists.linux.dev, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] net: dev: Convert sa_data to flexible array in struct sockaddr
Date: Tue, 25 Oct 2022 21:30:16 +0000	[thread overview]
Message-ID: <166673341646.9987.5803101009027995896.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221018095503.never.671-kees@kernel.org>

Hello:

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

On Tue, 18 Oct 2022 02:56:03 -0700 you wrote:
> One of the worst offenders of "fake flexible arrays" is struct sockaddr,
> as it is the classic example of why GCC and Clang have been traditionally
> forced to treat all trailing arrays as fake flexible arrays: in the
> distant misty past, sa_data became too small, and code started just
> treating it as a flexible array, even though it was fixed-size. The
> special case by the compiler is specifically that sizeof(sa->sa_data)
> and FORTIFY_SOURCE (which uses __builtin_object_size(sa->sa_data, 1))
> do not agree (14 and -1 respectively), which makes FORTIFY_SOURCE treat
> it as a flexible array.
> 
> [...]

Here is the summary with links:
  - [next] net: dev: Convert sa_data to flexible array in struct sockaddr
    https://git.kernel.org/netdev/net-next/c/b5f0de6df6dc

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



      parent reply	other threads:[~2022-10-25 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  9:56 [PATCH][next] net: dev: Convert sa_data to flexible array in struct sockaddr Kees Cook
2022-10-20  8:58 ` Paolo Abeni
2022-10-22  1:52   ` Kees Cook
2022-10-25 21:30 ` 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=166673341646.9987.5803101009027995896.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alibuda@linux.alibaba.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=dylany@fb.com \
    --cc=edumazet@google.com \
    --cc=imagedong@tencent.com \
    --cc=jk@codeconstruct.com.au \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=leon@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liu3101@purdue.edu \
    --cc=liuhangbin@gmail.com \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pablo@netfilter.org \
    --cc=petrm@nvidia.com \
    --cc=syzkaller@googlegroups.com \
    --cc=trix@redhat.com \
    --cc=willemb@google.com \
    --cc=william.xuanziyang@huawei.com \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=yajun.deng@linux.dev \
    /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.