From: behanw@converseincode.com
To: davem@davemloft.net
Cc: pablo@netfilter.org, kaber@trash.net, kadlec@blackhole.kfki.hu,
netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
coreteam@netfilter.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, dwmw2@infradead.org,
pageexec@freemail.hu, "Mark Charlebois" <charlebm@gmail.com>,
"Behan Webster" <behanw@converseincode.com>,
"Vinícius Tinti" <viniciustinti@gmail.com>
Subject: [PATCH v2] net: netfilter: LLVMLinux: vlais-netfilter
Date: Mon, 17 Mar 2014 23:12:01 -0700 [thread overview]
Message-ID: <1395123121-27053-1-git-send-email-behanw@converseincode.com> (raw)
In-Reply-To: <022D9517-4804-47BB-B789-CCF25F25C1ED@me.com>
From: Mark Charlebois <charlebm@gmail.com>
Replaced non-standard C use of Variable Length Arrays In Structs (VLAIS) in
xt_repldata.h with a C99 compliant flexible array member and then calculated
offsets to the other struct members. These other members aren't referenced by
name in this code, however this patch maintains the same memory layout and
padding as was previously accomplished using VLAIS.
Had the original structure been ordered differently, with the entries VLA at
the end, then it could have been a flexible member, and this patch would have
been a lot simpler. However since the data stored in this structure is
ultimately exported to userspace, the order of this structure can't be changed.
This patch makes no attempt to change the existing behavior, merely the way in
which the current layout is accomplished using standard C99 constructs. As such
the code can now be compiled with either gcc or clang.
Author: Mark Charlebois <charlebm@gmail.com>
Signed-off-by: Mark Charlebois <charlebm@gmail.com>
Signed-off-by: Behan Webster <behanw@converseincode.com>
Signed-off-by: Vinícius Tinti <viniciustinti@gmail.com>
---
net/netfilter/xt_repldata.h | 33 +++++++++++++++++++++++++++------
1 file changed, 27 insertions(+), 6 deletions(-)
diff --git a/net/netfilter/xt_repldata.h b/net/netfilter/xt_repldata.h
index 6efe4e5..f83a519 100644
--- a/net/netfilter/xt_repldata.h
+++ b/net/netfilter/xt_repldata.h
@@ -5,29 +5,50 @@
* they serve as the hanging-off data accessed through repl.data[].
*/
+/* tbl has the following structure equivalent, but is C99 compliant:
+ * struct {
+ * struct type##_replace repl;
+ * struct type##_standard entries[nhooks];
+ * struct type##_error term;
+ * } *tbl;
+ */
+
#define xt_alloc_initial_table(type, typ2) ({ \
unsigned int hook_mask = info->valid_hooks; \
unsigned int nhooks = hweight32(hook_mask); \
unsigned int bytes = 0, hooknum = 0, i = 0; \
struct { \
struct type##_replace repl; \
- struct type##_standard entries[nhooks]; \
- struct type##_error term; \
- } *tbl = kzalloc(sizeof(*tbl), GFP_KERNEL); \
+ char data[0]; \
+ } *tbl; \
+ struct type##_standard *entries; \
+ struct type##_error *term; \
+ size_t entries_offset = (-sizeof(tbl->repl)) & \
+ (__alignof__(*entries)-1); \
+ size_t entries_end = entries_offset + nhooks * sizeof(*entries); \
+ size_t term_offset = entries_end + \
+ (-sizeof(tbl->repl) - entries_end) & (__alignof__(*term)-1); \
+ size_t term_end = term_offset + sizeof(*term); \
+ size_t data_sz = term_end + \
+ (-sizeof(tbl->repl) - term_end) & (__alignof__(tbl->repl)-1); \
+ size_t tbl_sz = sizeof(tbl->repl) + data_sz; \
+ tbl = kzalloc(tbl_sz, GFP_KERNEL); \
if (tbl == NULL) \
return NULL; \
+ entries = (struct type##_standard *)&tbl->data[entries_offset]; \
+ term = (struct type##_error *)&tbl->data[term_offset]; \
strncpy(tbl->repl.name, info->name, sizeof(tbl->repl.name)); \
- tbl->term = (struct type##_error)typ2##_ERROR_INIT; \
+ *term = (struct type##_error)typ2##_ERROR_INIT; \
tbl->repl.valid_hooks = hook_mask; \
tbl->repl.num_entries = nhooks + 1; \
tbl->repl.size = nhooks * sizeof(struct type##_standard) + \
- sizeof(struct type##_error); \
+ sizeof(struct type##_error); \
for (; hook_mask != 0; hook_mask >>= 1, ++hooknum) { \
if (!(hook_mask & 1)) \
continue; \
tbl->repl.hook_entry[hooknum] = bytes; \
tbl->repl.underflow[hooknum] = bytes; \
- tbl->entries[i++] = (struct type##_standard) \
+ entries[i++] = (struct type##_standard) \
typ2##_STANDARD_INIT(NF_ACCEPT); \
bytes += sizeof(struct type##_standard); \
} \
--
1.8.3.2
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2014-03-18 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <022D9517-4804-47BB-B789-CCF25F25C1ED@me.com>
2014-03-18 6:12 ` behanw [this message]
2014-03-18 9:41 ` [PATCH v2] net: netfilter: LLVMLinux: vlais-netfilter David Laight
2014-03-18 14:47 ` Behan Webster
2014-03-18 15:24 ` David Laight
2014-03-18 17:37 ` Behan Webster
2014-03-19 1:50 ` [PATCH v3] " behanw
2014-03-19 9:52 ` David Laight
2014-03-19 17:25 ` Mark Charlebois
2014-03-23 6:55 ` [PATCH v4] " behanw
2014-04-18 0:40 ` Behan Webster
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=1395123121-27053-1-git-send-email-behanw@converseincode.com \
--to=behanw@converseincode.com \
--cc=charlebm@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=pageexec@freemail.hu \
--cc=viniciustinti@gmail.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;
as well as URLs for NNTP newsgroup(s).