From: Greg KH <gregkh@linuxfoundation.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: stable@vger.kernel.org, Johannes Berg <johannes@sipsolutions.net>,
Kees Cook <keescook@chromium.org>, Kalle Valo <kvalo@kernel.org>,
Koen Vandeputte <koen.vandeputte@citymesh.com>
Subject: Re: Please backport 2ae5c9248e06 ("wifi: mac80211: Use flexible array in struct ieee80211_tim_ie")
Date: Mon, 1 Jul 2024 14:26:03 +0200 [thread overview]
Message-ID: <2024070120-celestial-economist-32de@gregkh> (raw)
In-Reply-To: <b77e4ae4-fea5-4032-9d76-fbefc1c5dc65@quicinc.com>
On Thu, Jun 27, 2024 at 07:44:48AM -0700, Jeff Johnson wrote:
> On 6/27/2024 12:18 AM, Greg KH wrote:
> > On Wed, Jun 26, 2024 at 11:32:22AM -0700, Jeff Johnson wrote:
> >> Refer to:
> >> https://lore.kernel.org/all/CAPh3n83zb1PwFBFijJKChBqY95zzpYh=2iPf8tmh=YTS6e3xPw@mail.gmail.com/
> >
> > Please provide the information in the email, for those of us traveling
> > with store-and-forward email systems, links don't always work.
>
> Apologies. I was trying to be concise, but over did it.
>
> The issue reported is a splat in 6.6 due to FORTIFY_SOURCE complaining about
> access to an "old style" variable array declared with size 1:
> u8 virtual_map[1];
>
> >> Looks like this should be backported to all LTS kernels where FORTIFY_SOURCE
> >> is expected to be enabled.
> >
> > And where would that exactly be? Have you verified that it will apply
> > properly to those unnamed kernel trees?
>
> I don't know which trees are actively enabling FORTIFY_SOURCE. Since the
> report is coming from 6.6, I would expect we should backport at least to there.
It does not apply to 6.6.y, sorry, please provide a working backport for
any tree you wish to see this applied to.
thanks,
greg k-h
prev parent reply other threads:[~2024-07-01 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 18:32 Please backport 2ae5c9248e06 ("wifi: mac80211: Use flexible array in struct ieee80211_tim_ie") Jeff Johnson
2024-06-27 7:18 ` Greg KH
2024-06-27 14:44 ` Jeff Johnson
2024-06-27 16:55 ` Kees Cook
2024-07-01 12:26 ` Greg KH [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=2024070120-celestial-economist-32de@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=keescook@chromium.org \
--cc=koen.vandeputte@citymesh.com \
--cc=kvalo@kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=stable@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