From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Miklos Szeredi <miklos@szeredi•hu>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
James Morris <jmorris@namei•org>,
"Serge E. Hallyn" <serge@hallyn•com>,
linux-security-module@vger•kernel.org
Subject: linux-next: build failure after merge of the overlayfs tree
Date: Wed, 3 Jun 2020 11:51:27 +1000 [thread overview]
Message-ID: <20200603115127.28b01992@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
Hi all,
After merging the overlayfs tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: modpost: "security_file_ioctl" [fs/overlayfs/overlay.ko] undefined!
Caused by commit
b5940870e166 ("ovl: call secutiry hook in ovl_real_ioctl()")
I have applied this patch for today.
From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Wed, 3 Jun 2020 11:44:19 +1000
Subject: [PATCH] export security_file_ioctl
Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
security/security.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/security/security.c b/security/security.c
index 51de970fbb1e..077ac86faacf 100644
--- a/security/security.c
+++ b/security/security.c
@@ -1459,6 +1459,7 @@ int security_file_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
{
return call_int_hook(file_ioctl, 0, file, cmd, arg);
}
+EXPORT_SYMBOL_GPL(security_file_ioctl);
static inline unsigned long mmap_prot(struct file *file, unsigned long prot)
{
--
2.26.2
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-06-03 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 1:51 Stephen Rothwell [this message]
2020-06-03 7:57 ` linux-next: build failure after merge of the overlayfs tree Miklos Szeredi
-- strict thread matches above, loose matches on Subject: below --
2021-08-18 23:39 Stephen Rothwell
2021-09-02 23:03 ` Stephen Rothwell
2021-09-02 23:17 ` Linus Torvalds
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=20200603115127.28b01992@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jmorris@namei$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-security-module@vger$(echo .)kernel.org \
--cc=miklos@szeredi$(echo .)hu \
--cc=serge@hallyn$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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