[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1287653604.13326.8.camel@este.odu>
Date: Thu, 21 Oct 2010 11:33:24 +0200
From: KOVACS Krisztian <hidden@...abit.hu>
To: Jan Engelhardt <jengelh@...ozas.de>
Cc: netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
Patrick McHardy <kaber@...sh.net>,
David Miller <davem@...emloft.net>
Subject: Re: [PATCH 7/9] tproxy: added IPv6 support to the TPROXY target
Hi,
On Thu, 2010-10-21 at 11:14 +0200, Jan Engelhardt wrote:
> On Thursday 2010-10-21 10:50, KOVACS Krisztian wrote:
>
> >Hi,
> >
> >On Thu, 2010-10-21 at 10:47 +0200, Jan Engelhardt wrote:
> >> On Wednesday 2010-10-20 13:21, KOVACS Krisztian wrote:
> >> >
> >> > /* TPROXY target is capable of marking the packet to perform
> >> > * redirection. We can get rid of that whenever we get support for
> >> > * mutliple targets in the same rule. */
> >> >-struct xt_tproxy_target_info {
> >> >+struct xt_tproxy_target_info_v0 {
> >> > u_int32_t mark_mask;
> >> > u_int32_t mark_value;
> >> > __be32 laddr;
> >> > __be16 lport;
> >> > };
> >>
> >> You cannot change the struct name either, or it may break userspace
> >> compilations.
> >
> >True, though iptables has its own copy of the header anyway.
>
> There is - or so I always hear - other userspace programs.
>
> As for iptables, we only do the copy so that it compiles independent of
> the kernel version. You have to assume that the headers can be updated
> at any time.
Sure, I wasn't implying we shouldn't fix this in the patch, I just doubt
there's anything else other than iptables using this and iptables itself
isn't affected.
Anyway, I've fixed it. Thanks, Jan.
--KK
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists