Hi folks,
The second part of the changes I made as part of my work on the
compatibility headers concerned namespace pollution.
The problem was the following. My module is doing relatively high
level stuff in the kernel. It interracts with the network stack,
netfilter, the socket layer, etc. It does not deals with low-level
driver stuff. The issue was that including <linux/compat.h> bring a
_huge_ quantity of dependency with it, interrupt, thread, sysfs...
This is problematic as for some compilation unit, I should include as
few Linux header as possible (understand: if I don't include
<linux/tcp.h>, I don't want it included behind my back).
In order to workaround the problem, I simply wrapped every accessors
and struct definition within #ifdef checking if the parent header is
in use or not.
Considering the following exemple:
2.6.22:
static inline unsigned char *
skb_network_header(const struct sk_buff *skb)
{
return skb->nh.raw;
}
[...]
static inline struct iphdr *
ip_hdr(const struct sk_buff *skb)
{
return (struct iphdr *)skb_network_header(skb);
}
static inline unsigned int
ip_hdrlen(const struct sk_buff *skb)
{
return ip_hdr(skb)->ihl * 4;
}
Every compilation unit would need to have both <linux/skbuff.h>,
<linux/ip.h> and <net/ip.h> included. If the useful code does not
deals about networking, that's just pollution.
The solution I propose would transform this to:
2.6.22:
/* <linux/skbuff.h> */
#ifdef _LINUX_SKBUFF_H
static inline unsigned char *
skb_network_header(const struct sk_buff *skb)
{
return skb->nh.raw;
}
#endif
[...]
/* <linux/ip.h> */
#ifdef _LINUX_IP_H
static inline struct iphdr *
ip_hdr(const struct sk_buff *skb)
{
return (struct iphdr *)skb_network_header(skb);
}
#endif
/* <net/ip.h> */
#ifdef _IP_H
static inline unsigned int
ip_hdrlen(const struct sk_buff *skb)
{
return ip_hdr(skb)->ihl * 4;
}
#endif
That way, if the original code did not include the headers, it will
just not get the compat definition. The macro checked is the one used
as re-inclusion guard from the parent header which should be stable,
but even if it changes, supporting the new is trivial. With this
solution, the compat headers no longer needs to import all the headers
it is providing compatibililty to, but just let the original source
tells it what it needs compatibility for.
I will send as answer to mail a proof of concept for 2.6.22
Comments welcome,
- Arnaud
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
