From: Kees Cook <keescook@chromium.org>
To: David Howells <dhowells@redhat.com>
Cc: Jeff Layton <jlayton@kernel.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] netfs: Use container_of() for offset casting
Date: Wed, 18 May 2022 13:21:07 -0700 [thread overview]
Message-ID: <202205181229.E12F85BBBE@keescook> (raw)
In-Reply-To: <2692904.1652861114@warthog.procyon.org.uk>
On Wed, May 18, 2022 at 09:05:14AM +0100, David Howells wrote:
> [...]
> I don't want to do the following, say:
>
>
> struct afs_vnode {
> struct netfs_i_c_pair ni;
> ...
> };
>
> as that would then require a lot of s/->vfs_inode/->ni.vfs_inode/, but maybe
> it would be better to include a struct inode in struct netfs_i_context, and
Right; that's why I kept the struct internal -- the implicit ordering of
inode and netfs_i_context is already present in all the users.
> On the other hand:
>
> warthog>git grep '[>.]vfs_inode' -- fs/{9p,afs,ceph,cifs,nfs} | wc -l
> 181
That seems painful. Maybe _new_ users of netfs could be written to use
the proposed netfs_inode:
> so maybe a mass change to, say:
>
> struct netfs_inode {
> struct inode vfs_inode;
> ...
> };
Better yet, netfs can define a macro helper. I'll send a v2...
--
Kees Cook
prev parent reply other threads:[~2022-05-18 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 21:02 [PATCH] netfs: Use container_of() for offset casting Kees Cook
2022-05-17 22:32 ` Jeff Layton
2022-05-18 8:05 ` David Howells
2022-05-18 10:01 ` David Laight
2022-05-18 15:21 ` David Howells
2022-05-18 20:21 ` 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=202205181229.E12F85BBBE@keescook \
--to=keescook@chromium.org \
--cc=dhowells@redhat.com \
--cc=jlayton@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