定义Netfilter钩子函数的正确方法是什么?

时间:2014-08-04 17:11:48

标签: linux linux-kernel netfilter

我正在为Linux编写内核模块(更具体地说,是一个 Netfilter 模块)。我试图让它与各种内核兼容,但是输入功能给我带来了麻烦。

从LXR,我可以看到内核3.13中的nf_hookfn typedef发生了变化。

Linux 3.12 and before

typedef unsigned int nf_hookfn(unsigned int hooknum, (...));

3.13 onwards:

typedef unsigned int nf_hookfn(const struct nf_hook_ops *ops, (...));

但是,我们有一台Red Hat机器声称使用内核3.10.0-123.4.4.el7.x86_64,但其netlink.h读取

typedef unsigned int nf_hookfn(const struct nf_hook_ops *ops, (...));

好像它是3.13+代码。

它在我的模块上引起了警告,因为它彻底破坏了我根据内核版本以不同方式定义函数的尝试:

#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 13, 0)
#define HOOK_ARG_TYPE const struct nf_hook_ops *
#else
#define HOOK_ARG_TYPE unsigned int
#endif

我错过了什么文件?没有任何东西向我建议内核API依赖于BOTH内核版本和发行版,这没有任何意义。

更重要的是,我该如何解决这个问题? nf_hookfn是一个typedef,而不是一个宏,所以我不能把它放在我的函数定义上。 可能使事情变得更容易的一件事是我从不使用那一个论点。

当然,我不是第一个经历过这种情况的人吗?我的意思是nf_hookfn是任何Netfilter模块的入口点;你认为他们通过改变它来打破成千上万的司机。

2 个答案:

答案 0 :(得分:2)

最后,我刚刚提出entire module致力于此:

/**
 * The kernel API is far from static. In particular, the Netfilter packet entry
 * function keeps changing. nf_hook.c, the file where we declare our packet
 * entry function, has been quite difficult to read for a while now. It's pretty
 * amusing, because we don't even use any of the noisy arguments.
 *
 * This file declares a usable function header that abstracts away all those
 * useless arguments.
 */

#include <linux/version.h>

/* If this is a Red Hat-based kernel (Red Hat, CentOS, Fedora, etc)... */
#ifdef RHEL_RELEASE_CODE

#if RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(7, 2)
#define NF_CALLBACK(name, skb) unsigned int name( \
        const struct nf_hook_ops *ops, \
        struct sk_buff *skb, \
        const struct net_device *in, \
        const struct net_device *out, \
        const struct nf_hook_state *state) \

#elif RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(7, 0)
#define NF_CALLBACK(name, skb) unsigned int name( \
        const struct nf_hook_ops *ops, \
        struct sk_buff *skb, \
        const struct net_device *in, \
        const struct net_device *out, \
        int (*okfn)(struct sk_buff *))

#else

/*
 * Sorry, I don't have headers for RHEL 6 and below because I'm in a bit of a
 * deadline right now.
 * If this is causing you trouble, find `nf_hookfn` in your kernel headers
 * (typically in include/linux/netfilter.h) and add your version of the
 * NF_CALLBACK macro here.
 * Also, kernel headers per version can be found here: http://vault.centos.org/
 */
#error "Sorry; this version of RHEL is not supported because it's kind of old."

#endif /* RHEL_RELEASE_CODE >= x */


/* If this NOT a RedHat-based kernel (Ubuntu, Debian, SuSE, etc)... */
#else

#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 4, 0)
#define NF_CALLBACK(name, skb) unsigned int name( \
        void *priv, \
        struct sk_buff *skb, \
        const struct nf_hook_state *state)

#elif LINUX_VERSION_CODE >= KERNEL_VERSION(4, 1, 0)
#define NF_CALLBACK(name, skb) unsigned int name( \
        const struct nf_hook_ops *ops, \
        struct sk_buff *skb, \
        const struct nf_hook_state *state)

#elif LINUX_VERSION_CODE >= KERNEL_VERSION(3, 13, 0)
#define NF_CALLBACK(name, skb) unsigned int name( \
        const struct nf_hook_ops *ops, \
        struct sk_buff *skb, \
        const struct net_device *in, \
        const struct net_device *out, \
        int (*okfn)(struct sk_buff *))

#elif LINUX_VERSION_CODE >= KERNEL_VERSION(3, 0, 0)
#define NF_CALLBACK(name, skb) unsigned int name( \
        unsigned int hooknum, \
        struct sk_buff *skb, \
        const struct net_device *in, \
        const struct net_device *out, \
        int (*okfn)(struct sk_buff *))

#else
#error "Linux < 3.0 isn't supported at all."

#endif /* LINUX_VERSION_CODE > n */

#endif /* RHEL or not RHEL */

所以不要这样:

static unsigned int function_name((...), struct sk_buff *skb, (...))
{
    return do_something_with_skb(skb);
}

这样做:

static NF_CALLBACK(function_name, skb)
{
    return do_something_with_skb(skb);
}

答案 1 :(得分:1)

可能你正在使用ko,它是为更新版本的内核编译的。如果模块未作为RH发货,那么您可能需要与供应商合作才能解决此问题。