From: Christoph Hellwig <hch@infradead.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Use container_of() for gfs2_glock(aspace)
Date: Tue, 10 May 2022 00:13:30 -0700 [thread overview]
Message-ID: <YnoQmuPgK9c5V8ZC@infradead.org> (raw)
In-Reply-To: <20220508100630.2642320-1-keescook@chromium.org>
> +/* gfs2_glock_get(), "glock" must be first. */
> +struct glock_aspace {
> + struct gfs2_glock glock;
> + struct address_space mapping;
> +};
Why does glock need to be first? The whole point of using container_of
is that we don't have to make that assumption.
> static inline struct address_space *gfs2_glock2aspace(struct gfs2_glock *gl)
> {
> if (gl->gl_ops->go_flags & GLOF_ASPACE)
> - return (struct address_space *)(gl + 1);
> + return &(container_of(gl, struct glock_aspace, glock)->mapping);
Do we even need the braces here?
> struct inode *inode = mapping->host;
> if (mapping->a_ops == &gfs2_meta_aops)
> - return (((struct gfs2_glock *)mapping) - 1)->gl_name.ln_sbd;
> + return container_of(mapping, struct glock_aspace, mapping)->glock.gl_name.ln_sbd;
A local variable would be really nice for the reader here to decompose
this a bit:
struct glock_aspace *a =
container_of(mapping, struct glock_aspace, mapping);
return a->glock.gl_name.ln_sbd;
next prev parent reply other threads:[~2022-05-10 7:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 10:06 [Cluster-devel] [PATCH] gfs2: Use container_of() for gfs2_glock(aspace) Kees Cook
2022-05-10 7:13 ` Christoph Hellwig [this message]
2022-05-10 11:13 ` Andreas Gruenbacher
2022-05-10 15:51 ` Kees Cook
2022-05-10 16:16 ` Andreas Gruenbacher
2022-05-10 17:55 ` 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=YnoQmuPgK9c5V8ZC@infradead.org \
--to=hch@infradead.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).