From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
"Luis R. Rodriguez" <lrodriguez@qca.qualcomm.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: [PATCH 2/2] compat: implement dummy security_sk_clone
Date: Wed, 16 Nov 2011 19:39:34 -0500 [thread overview]
Message-ID: <1321490374-24529-2-git-send-email-linville@tuxdriver.com> (raw)
In-Reply-To: <1321490374-24529-1-git-send-email-linville@tuxdriver.com>
This has been defined in include/linux/security.h for some time, but was
only given an EXPORT_SYMBOL for 3.2. Add a compat_* definition to avoid
breaking the module load with an undefined symbol.
Signed-off-by: John W. Linville <linville@tuxdriver.com>
---
include/linux/compat-3.2.h | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/include/linux/compat-3.2.h b/include/linux/compat-3.2.h
index ceaaecc..08f102f 100644
--- a/include/linux/compat-3.2.h
+++ b/include/linux/compat-3.2.h
@@ -72,6 +72,17 @@ static inline char *hex_byte_pack(char *buf, u8 byte)
return buf;
}
+/*
+ * This has been defined in include/linux/security.h for some time, but was
+ * only given an EXPORT_SYMBOL for 3.2. Add a compat_* definition to avoid
+ * breaking the compile.
+ */
+#define security_sk_clone(a, b) compat_security_sk_clone(a, b)
+
+static inline void security_sk_clone(const struct sock *sk, struct sock *newsk)
+{
+}
+
#endif /* (LINUX_VERSION_CODE < KERNEL_VERSION(3,2,0)) */
#endif /* LINUX_3_2_COMPAT_H */
--
1.7.4.4
next prev parent reply other threads:[~2011-11-17 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 0:39 [PATCH 1/2] compat: avoid warning in compat_system_workqueue_create John W. Linville
2011-11-17 0:39 ` John W. Linville [this message]
2011-11-18 19:37 ` [PATCH 2/2] compat: implement dummy security_sk_clone Hauke Mehrtens
2011-11-18 20:53 ` John W. Linville
2011-11-18 19:24 ` [PATCH 1/2] compat: avoid warning in compat_system_workqueue_create Hauke Mehrtens
2011-11-18 19:32 ` Luis R. Rodriguez
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=1321490374-24529-2-git-send-email-linville@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@qca.qualcomm.com \
/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