From: David Laight <David.Laight@ACULAB.COM>
To: 'David Howells' <dhowells@redhat.com>, Kees Cook <keescook@chromium.org>
Cc: Jeff Layton <jlayton@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>
Subject: RE: [PATCH] netfs: Use container_of() for offset casting
Date: Wed, 18 May 2022 10:01:27 +0000 [thread overview]
Message-ID: <aa9e13f50be440a192b6acbce422db96@AcuMS.aculab.com> (raw)
In-Reply-To: <2692904.1652861114@warthog.procyon.org.uk>
From: David Howells
> Sent: 18 May 2022 09:05
>
> I wonder if it would be worth making this explicit in the inode wrappers of
> the users of netfslib. In afs, for instance, there is:
>
> struct afs_vnode {
> struct {
> /* These must be contiguous */
> struct inode vfs_inode;
> struct netfs_i_context netfs_ctx;
> };
> ...
> };
>
> would it be worth making that:
>
> struct afs_vnode {
> union {
> struct netfs_i_c_pair netfs_inode;
> struct {
> /* These must be contiguous */
> struct inode vfs_inode;
> struct netfs_i_context netfs_ctx;
> };
> };
> ...
> };
>
Can't you just name the structure so it is:
struct afs_vnode {
struct netfs_i_c_pair {
/* These must be contiguous */
struct inode vfs_inode;
struct netfs_i_context netfs_ctx;
};
...
};
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-05-18 10:01 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 [this message]
2022-05-18 15:21 ` David Howells
2022-05-18 20:21 ` 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=aa9e13f50be440a192b6acbce422db96@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=keescook@chromium.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