From: Randy Dunlap <rdunlap@infradead.org>
To: linux-security-module <linux-security-module@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: David Howells <dhowells@redhat.com>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: [PATCH -next] security: smack: add watch_queue.h header to fix build errors
Date: Thu, 10 Oct 2019 08:24:26 -0700 [thread overview]
Message-ID: <0f9adf0a-36b2-81a2-acee-1f9b24cea0bd@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Fix build errors when CONFIG_WATCH_QUEUE=y by adding the
appropriate header file.
../security/smack/smack_lsm.c: In function ‘smack_post_notification’:
../security/smack/smack_lsm.c:4384:7: error: dereferencing pointer to incomplete type ‘struct watch_notification’
if (n->type == WATCH_TYPE_META)
^~
../security/smack/smack_lsm.c:4384:17: error: ‘WATCH_TYPE_META’ undeclared (first use in this function); did you mean ‘TCA_PIE_BETA’?
if (n->type == WATCH_TYPE_META)
^~~~~~~~~~~~~~~
TCA_PIE_BETA
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Casey Schaufler <casey@schaufler-ca.com>
Cc: David Howells <dhowells@redhat.com>
Cc: linux-security-module@vger.kernel.org
---
security/smack/smack_lsm.c | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20191010.orig/security/smack/smack_lsm.c
+++ linux-next-20191010/security/smack/smack_lsm.c
@@ -42,6 +42,7 @@
#include <linux/parser.h>
#include <linux/fs_context.h>
#include <linux/fs_parser.h>
+#include <linux/watch_queue.h>
#include "smack.h"
#define TRANS_TRUE "TRUE"
next reply other threads:[~2019-10-10 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 15:24 Randy Dunlap [this message]
2019-10-11 7:54 ` [PATCH -next] security: smack: add watch_queue.h header to fix build errors 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=0f9adf0a-36b2-81a2-acee-1f9b24cea0bd@infradead.org \
--to=rdunlap@infradead.org \
--cc=casey@schaufler-ca.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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).