linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Kees Cook <keescook@chromium.org>, Hans de Goede <hdegoede@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH] vboxsf: Use flexible arrays for trailing string member
Date: Tue, 8 Aug 2023 14:20:06 -0500	[thread overview]
Message-ID: <20fc56ef-6240-e86e-6d38-9278592a3b25@lwfinger.net> (raw)
In-Reply-To: <169040854617.1782642.4557415464507636357.b4-ty@chromium.org>

On 7/26/23 16:55, Kees Cook wrote:
> 
> On Thu, 20 Jul 2023 08:15:06 -0700, Kees Cook wrote:
>> The declaration of struct shfl_string used trailing fake flexible arrays
>> for the string member. This was tripping FORTIFY_SOURCE since commit
>> df8fc4e934c1 ("kbuild: Enable -fstrict-flex-arrays=3"). Replace the
>> utf8 and utf16 members with actual flexible arrays, drop the unused ucs2
>> member, and retriain a 2 byte padding to keep the structure size the same.
>>
>>
>> [...]
> 
> Applied to for-linus/hardening, thanks!
> 
> [1/1] vboxsf: Use flexible arrays for trailing string member
>        https://git.kernel.org/kees/c/a8f014ec6a21

Kees,

This patch has not been applied to kernel 6.5-rc5. Is there some problem?

Larry



  reply	other threads:[~2023-08-08 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 15:15 [PATCH] vboxsf: Use flexible arrays for trailing string member Kees Cook
2023-07-25  9:00 ` Hans de Goede
2023-07-26 21:55 ` Kees Cook
2023-08-08 19:20   ` Larry Finger [this message]
2023-08-08 21:01     ` Kees Cook

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=20fc56ef-6240-e86e-6d38-9278592a3b25@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=hdegoede@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).