From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Koen Vandeputte <koen.vandeputte@citymesh.com>,
Johannes Berg <johannes@sipsolutions.net>,
Kees Cook <keescook@chromium.org>
Cc: <ath10k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: ieee80211.h virtual_map splat
Date: Fri, 21 Jun 2024 07:25:08 -0700 [thread overview]
Message-ID: <d834ff59-f331-4eb4-91c6-e76eb48780d8@quicinc.com> (raw)
In-Reply-To: <CAPh3n80PF4NULjKJVVMEiGuuJZhLQszYSTCv+f6e9LfVJbKesw@mail.gmail.com>
On 6/21/2024 3:31 AM, Koen Vandeputte wrote:
> On Fri, Jun 21, 2024 at 11:30 AM Johannes Berg
> <johannes@sipsolutions.net> wrote:
>>
>>
>>> will this one get backported also?
>>
>> Why? It's not even a bug.
>>
>> johannes
>
> Because without this patch, it produces a splat on kernel 6.6 (which
> is an LTS) at least ? :-)
@Kees, have you been backporting all your flexible array changes?
Or are you suggesting folks disable FORTIFY_SOURCE (is that the controlling
config?)
thread starts with:
https://lore.kernel.org/all/CAPh3n83zb1PwFBFijJKChBqY95zzpYh=2iPf8tmh=YTS6e3xPw@mail.gmail.com/
/jeff
next prev parent reply other threads:[~2024-06-21 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 8:04 ieee80211.h virtual_map splat Koen Vandeputte
2024-06-21 8:21 ` Johannes Berg
2024-06-21 8:47 ` Koen Vandeputte
2024-06-21 9:30 ` Johannes Berg
2024-06-21 10:31 ` Koen Vandeputte
2024-06-21 14:25 ` Jeff Johnson [this message]
2024-06-21 19:46 ` Kees Cook
2024-06-25 3:44 ` Jeff Johnson
2024-06-25 6:56 ` Kalle Valo
2024-06-25 15:02 ` Jakub Kicinski
2024-06-25 15:25 ` Kalle Valo
2024-06-26 18:11 ` Kees Cook
2024-06-26 18:31 ` Jeff Johnson
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=d834ff59-f331-4eb4-91c6-e76eb48780d8@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=ath10k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=keescook@chromium.org \
--cc=koen.vandeputte@citymesh.com \
--cc=linux-wireless@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