From: David Howells <dhowells@redhat.com>
To: viro@ZenIV.linux.org.uk, miklos@szeredi.hu
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
linux-unionfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Overlayfs: ovl_fill_merge() should use container_of() rather than direct cast
Date: Thu, 30 Oct 2014 14:10:05 +0000 [thread overview]
Message-ID: <20141030141004.28203.79687.stgit@warthog.procyon.org.uk> (raw)
ovl_fill_merge() effectively directly casts the buf pointer to an
ovl_readdir_data struct pointer, but the pointer actually points to the
dir_context struct contained therein.
So use container_of() instead.
Signed-off-by: David Howells <dhowells@redhat.com>
---
fs/overlayfs/readdir.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/overlayfs/readdir.c b/fs/overlayfs/readdir.c
index 910553f37aca..d142c2bf8f1e 100644
--- a/fs/overlayfs/readdir.c
+++ b/fs/overlayfs/readdir.c
@@ -181,7 +181,9 @@ static void ovl_cache_put(struct ovl_dir_file *od, struct dentry *dentry)
static int ovl_fill_merge(void *buf, const char *name, int namelen,
loff_t offset, u64 ino, unsigned int d_type)
{
- struct ovl_readdir_data *rdd = buf;
+ struct dir_context *ctx = buf;
+ struct ovl_readdir_data *rdd =
+ container_of(ctx, struct ovl_readdir_data, ctx);
rdd->count++;
if (!rdd->is_merge)
next reply other threads:[~2014-10-30 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 14:10 David Howells [this message]
2014-10-30 14:36 ` Miklos Szeredi
2014-10-30 14:47 ` David Howells
2014-10-30 16:37 ` Miklos Szeredi
2014-10-31 9:46 ` [PATCH fixed] vfs: make first argument of dir_context.actor typed Miklos Szeredi
2014-10-31 10:28 ` Al Viro
2014-10-31 10:18 ` [PATCH] Overlayfs: ovl_fill_merge() should use container_of() rather than direct cast David Howells
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=20141030141004.28203.79687.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@ZenIV.linux.org.uk \
/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
all inboxes | Powered by JetHome®