linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: David Sterba <dsterba@suse.cz>
Cc: David Sterba <dsterba@suse.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH] fs/affs: struct slink_front: Replace 1-element array with flexible array
Date: Thu, 11 Jul 2024 09:05:25 -0700	[thread overview]
Message-ID: <202407110901.AB3DEF0A@keescook> (raw)
In-Reply-To: <20240711142928.GB8022@suse.cz>

On Thu, Jul 11, 2024 at 04:29:28PM +0200, David Sterba wrote:
> On Wed, Jul 10, 2024 at 03:57:34PM -0700, Kees Cook wrote:
> > Replace the deprecated[1] use of a 1-element array in
> > struct slink_front with a modern flexible array.
> > 
> > No binary differences are present after this conversion.
> > 
> > Link: https://github.com/KSPP/linux/issues/79 [1]
> > Signed-off-by: Kees Cook <kees@kernel.org>
> 
> Thanks, I've added the 3 patches to my tree.

Thanks!

> I've noticed there's one
> more 1-element array in struct affs_root_head (hashtable):
> 
> https://elixir.bootlin.com/linux/latest/source/fs/affs/amigaffs.h#L50
> 
> The struct is used only partially by AFFS_ROOT_HEAD from affs_fill_super
> and not accessing the hashtable. This could have been missed by the
> tools you use or was the conversion intentionally skipped?

Yeah -- this was intentional. We wanted to finish conversion of members
that were actually being used by the kernel. There is a lot of UAPI and
"all possible data structures" structs declared in the kernel that we
were wading through only to find they weren't actually being used.

That said, I'm happy to send a patch to convert hashtable -- it's not
used so it can't break anything. ;)

-- 
Kees Cook

      reply	other threads:[~2024-07-11 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10 22:57 [PATCH] fs/affs: struct slink_front: Replace 1-element array with flexible array Kees Cook
2024-07-10 23:23 ` Gustavo A. R. Silva
2024-07-11 14:29 ` David Sterba
2024-07-11 16:05   ` Kees Cook [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=202407110901.AB3DEF0A@keescook \
    --to=kees@kernel.org \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --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).