From: "Serge E. Hallyn" <serge@hallyn.com>
To: James.Bottomley@HansenPartnership.com
Cc: Christian Brauner <christian.brauner@canonical.com>,
lkml <linux-kernel@vger.kernel.org>,
serge@hallyn.com
Subject: [PATCH 1/1] shiftfs: specify struct members
Date: Sun, 17 May 2020 16:25:25 -0500 [thread overview]
Message-ID: <20200517212525.GA29858@mail.hallyn.com> (raw)
struct path is declared as randomize_layout, so specify the
struct members when initializing to avoid build failure.
Signed-off-by: Serge Hallyn <shallyn@cisco.com>
---
[ this is for https://git.kernel.org/pub/scm/linux/kernel/git/jejb/binfmt_misc.git/commit/?h=shiftfs-v3 ,
which i was just building for an experiment ]
fs/shiftfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/shiftfs.c b/fs/shiftfs.c
index 7984a93745d2..6028244c2f42 100644
--- a/fs/shiftfs.c
+++ b/fs/shiftfs.c
@@ -535,7 +535,7 @@ static int shiftfs_getattr(const struct path *path, struct kstat *stat,
struct dentry *real = path->dentry->d_fsdata;
struct inode *reali = real->d_inode;
const struct inode_operations *iop = reali->i_op;
- struct path newpath = { path->dentry->d_sb->s_fs_info, real };
+ struct path newpath = { .mnt = path->dentry->d_sb->s_fs_info, .dentry = real };
int err = 0;
if (iop->getattr)
--
2.17.1
reply other threads:[~2020-05-17 21:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200517212525.GA29858@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=christian.brauner@canonical.com \
--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).