hit this yesterday, and havent had time to look at it, to see if its a
simple fix
MODPOST vmlinux.o
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
net/built-in.o: In function `handle_response_icmp':
ip_vs_core.c:(.text+0x2b5c4): undefined reference to `nf_conntrack_untracked'
net/built-in.o: In function `T.925':
ip_vs_core.c:(.text+0x2cbbd): undefined reference to `nf_conntrack_untracked'
net/built-in.o: In function `ip_vs_null_xmit':
(.text+0x310da): undefined reference to `nf_conntrack_untracked'
net/built-in.o: In function `ip_vs_tunnel_xmit':
(.text+0x311e3): undefined reference to `nf_conntrack_untracked'
net/built-in.o: In function `ip_vs_nat_xmit':
(.text+0x3176f): undefined reference to `nf_conntrack_untracked'
net/built-in.o:(.text+0x3199d): more undefined references to
`nf_conntrack_untracked' follow
make: *** [.tmp_vmlinux1] Error 1
has there been anything sent forward for this yet?
--
Justin P. Mattock
Le jeudi 18 novembre 2010 à 06:36 -0800, Justin Mattock a écrit :
> hit this yesterday, and havent had time to look at it, to see if its a
> simple fix
>
> MODPOST vmlinux.o
> WARNING: modpost: Found 1 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> GEN .version
> CHK include/generated/compile.h
> UPD include/generated/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> net/built-in.o: In function `handle_response_icmp':
> ip_vs_core.c:(.text+0x2b5c4): undefined reference to `nf_conntrack_untracked'
> net/built-in.o: In function `T.925':
> ip_vs_core.c:(.text+0x2cbbd): undefined reference to `nf_conntrack_untracked'
> net/built-in.o: In function `ip_vs_null_xmit':
> (.text+0x310da): undefined reference to `nf_conntrack_untracked'
> net/built-in.o: In function `ip_vs_tunnel_xmit':
> (.text+0x311e3): undefined reference to `nf_conntrack_untracked'
> net/built-in.o: In function `ip_vs_nat_xmit':
> (.text+0x3176f): undefined reference to `nf_conntrack_untracked'
> net/built-in.o:(.text+0x3199d): more undefined references to
> `nf_conntrack_untracked' follow
> make: *** [.tmp_vmlinux1] Error 1
>
> has there been anything sent forward for this yet?
>
Try to find out why net/netfilter/nf_conntrack_core.c is not compiled ?
./net/netfilter/nf_conntrack_core.c:65:DEFINE_PER_CPU(struct nf_conn, nf_conntrack_untracked);
./net/netfilter/nf_conntrack_core.c:66:EXPORT_PER_CPU_SYMBOL(nf_conntrack_untracked);
On 11/18/2010 07:12 AM, Eric Dumazet wrote:
> Le jeudi 18 novembre 2010 à 06:36 -0800, Justin Mattock a écrit :
>> hit this yesterday, and havent had time to look at it, to see if its a
>> simple fix
>>
>> MODPOST vmlinux.o
>> WARNING: modpost: Found 1 section mismatch(es).
>> To see full details build your kernel with:
>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>> GEN .version
>> CHK include/generated/compile.h
>> UPD include/generated/compile.h
>> CC init/version.o
>> LD init/built-in.o
>> LD .tmp_vmlinux1
>> net/built-in.o: In function `handle_response_icmp':
>> ip_vs_core.c:(.text+0x2b5c4): undefined reference to `nf_conntrack_untracked'
>> net/built-in.o: In function `T.925':
>> ip_vs_core.c:(.text+0x2cbbd): undefined reference to `nf_conntrack_untracked'
>> net/built-in.o: In function `ip_vs_null_xmit':
>> (.text+0x310da): undefined reference to `nf_conntrack_untracked'
>> net/built-in.o: In function `ip_vs_tunnel_xmit':
>> (.text+0x311e3): undefined reference to `nf_conntrack_untracked'
>> net/built-in.o: In function `ip_vs_nat_xmit':
>> (.text+0x3176f): undefined reference to `nf_conntrack_untracked'
>> net/built-in.o:(.text+0x3199d): more undefined references to
>> `nf_conntrack_untracked' follow
>> make: *** [.tmp_vmlinux1] Error 1
>>
>> has there been anything sent forward for this yet?
>>
>
> Try to find out why net/netfilter/nf_conntrack_core.c is not compiled ?
seems it is compiling, it's after the compiling when this breaks
>
> ./net/netfilter/nf_conntrack_core.c:65:DEFINE_PER_CPU(struct nf_conn, nf_conntrack_untracked);
> ./net/netfilter/nf_conntrack_core.c:66:EXPORT_PER_CPU_SYMBOL(nf_conntrack_untracked);
>
>
>
>
Justin P. Mattock
Le jeudi 18 novembre 2010 à 09:25 -0800, Justin P. Mattock a écrit :
> On 11/18/2010 07:12 AM, Eric Dumazet wrote:
> > Le jeudi 18 novembre 2010 à 06:36 -0800, Justin Mattock a écrit :
> >> hit this yesterday, and havent had time to look at it, to see if its a
> >> simple fix
> >>
> >> MODPOST vmlinux.o
> >> WARNING: modpost: Found 1 section mismatch(es).
> >> To see full details build your kernel with:
> >> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> >> GEN .version
> >> CHK include/generated/compile.h
> >> UPD include/generated/compile.h
> >> CC init/version.o
> >> LD init/built-in.o
> >> LD .tmp_vmlinux1
> >> net/built-in.o: In function `handle_response_icmp':
> >> ip_vs_core.c:(.text+0x2b5c4): undefined reference to `nf_conntrack_untracked'
> >> net/built-in.o: In function `T.925':
> >> ip_vs_core.c:(.text+0x2cbbd): undefined reference to `nf_conntrack_untracked'
> >> net/built-in.o: In function `ip_vs_null_xmit':
> >> (.text+0x310da): undefined reference to `nf_conntrack_untracked'
> >> net/built-in.o: In function `ip_vs_tunnel_xmit':
> >> (.text+0x311e3): undefined reference to `nf_conntrack_untracked'
> >> net/built-in.o: In function `ip_vs_nat_xmit':
> >> (.text+0x3176f): undefined reference to `nf_conntrack_untracked'
> >> net/built-in.o:(.text+0x3199d): more undefined references to
> >> `nf_conntrack_untracked' follow
> >> make: *** [.tmp_vmlinux1] Error 1
> >>
> >> has there been anything sent forward for this yet?
> >>
> >
> > Try to find out why net/netfilter/nf_conntrack_core.c is not compiled ?
>
> seems it is compiling, it's after the compiling when this breaks
>
> >
> > ./net/netfilter/nf_conntrack_core.c:65:DEFINE_PER_CPU(struct nf_conn, nf_conntrack_untracked);
> > ./net/netfilter/nf_conntrack_core.c:66:EXPORT_PER_CPU_SYMBOL(nf_conntrack_untracked);
> >
> >
> >
> >
>
> Justin P. Mattock
Let me guess...
net/netfilter/nf_conntrack_core is compiled as a module, and ip_vs
statically (in vmlinux) ?
CONFIG_NF_CONNTRACK=m
CONFIG_IP_VS=y
We probably need some Kconfig magic ;)
From: Eric Dumazet <[email protected]>
Date: Thu, 18 Nov 2010 18:48:17 +0100
> Let me guess...
>
> net/netfilter/nf_conntrack_core is compiled as a module, and ip_vs
> statically (in vmlinux) ?
>
> CONFIG_NF_CONNTRACK=m
> CONFIG_IP_VS=y
>
> We probably need some Kconfig magic ;)
Randy Dunlap made a similar report today with a sample .config
that triggers the problem.
I'll look into it after lunch.
Am 18.11.2010 18:50, schrieb David Miller:
> From: Eric Dumazet <[email protected]>
> Date: Thu, 18 Nov 2010 18:48:17 +0100
>
>> Let me guess...
>>
>> net/netfilter/nf_conntrack_core is compiled as a module, and ip_vs
>> statically (in vmlinux) ?
>>
>> CONFIG_NF_CONNTRACK=m
>> CONFIG_IP_VS=y
>>
>> We probably need some Kconfig magic ;)
>
> Randy Dunlap made a similar report today with a sample .config
> that triggers the problem.
>
> I'll look into it after lunch.
Thanks, I'll take care of this.
On 11/18/2010 09:50 AM, David Miller wrote:
> From: Eric Dumazet<[email protected]>
> Date: Thu, 18 Nov 2010 18:48:17 +0100
>
>> Let me guess...
>>
>> net/netfilter/nf_conntrack_core is compiled as a module, and ip_vs
>> statically (in vmlinux) ?
>>
>> CONFIG_NF_CONNTRACK=m
>> CONFIG_IP_VS=y
>>
>> We probably need some Kconfig magic ;)
>
> Randy Dunlap made a similar report today with a sample .config
> that triggers the problem.
>
> I'll look into it after lunch.
>
alright..
Justin P. Mattock
Am 18.11.2010 19:13, schrieb Justin P. Mattock:
> On 11/18/2010 09:50 AM, David Miller wrote:
>> From: Eric Dumazet<[email protected]>
>> Date: Thu, 18 Nov 2010 18:48:17 +0100
>>
>>> Let me guess...
>>>
>>> net/netfilter/nf_conntrack_core is compiled as a module, and ip_vs
>>> statically (in vmlinux) ?
>>>
>>> CONFIG_NF_CONNTRACK=m
>>> CONFIG_IP_VS=y
>>>
>>> We probably need some Kconfig magic ;)
>>
Please try whether this patch fixes the problem.
netfilter: fix IP_VS dependencies
When NF_CONNTRACK is enabled, IP_VS uses conntrack symbols.
Therefore IP_VS can't be linked statically when conntrack
is built modular.
Reported-by: Justin P. Mattock <[email protected]>
Signed-off-by: Patrick McHardy <[email protected]>
On 11/18/2010 10:20 AM, Patrick McHardy wrote:
> Am 18.11.2010 19:13, schrieb Justin P. Mattock:
>> On 11/18/2010 09:50 AM, David Miller wrote:
>>> From: Eric Dumazet<[email protected]>
>>> Date: Thu, 18 Nov 2010 18:48:17 +0100
>>>
>>>> Let me guess...
>>>>
>>>> net/netfilter/nf_conntrack_core is compiled as a module, and ip_vs
>>>> statically (in vmlinux) ?
>>>>
>>>> CONFIG_NF_CONNTRACK=m
>>>> CONFIG_IP_VS=y
>>>>
>>>> We probably need some Kconfig magic ;)
>>>
>
> Please try whether this patch fixes the problem.
sure.. right now I'm rebuilding with conntract built-in as suggested by
eric. then ill go back and test your patch out
>
> netfilter: fix IP_VS dependencies
>
> When NF_CONNTRACK is enabled, IP_VS uses conntrack symbols.
> Therefore IP_VS can't be linked statically when conntrack
> is built modular.
>
> Reported-by: Justin P. Mattock<[email protected]>
> Signed-off-by: Patrick McHardy<[email protected]>
>
>
Justin P. Mattock
On 11/18/2010 10:20 AM, Patrick McHardy wrote:
> Am 18.11.2010 19:13, schrieb Justin P. Mattock:
>> On 11/18/2010 09:50 AM, David Miller wrote:
>>> From: Eric Dumazet<[email protected]>
>>> Date: Thu, 18 Nov 2010 18:48:17 +0100
>>>
>>>> Let me guess...
>>>>
>>>> net/netfilter/nf_conntrack_core is compiled as a module, and ip_vs
>>>> statically (in vmlinux) ?
>>>>
>>>> CONFIG_NF_CONNTRACK=m
>>>> CONFIG_IP_VS=y
>>>>
>>>> We probably need some Kconfig magic ;)
>>>
>
> Please try whether this patch fixes the problem.
>
> netfilter: fix IP_VS dependencies
>
> When NF_CONNTRACK is enabled, IP_VS uses conntrack symbols.
> Therefore IP_VS can't be linked statically when conntrack
> is built modular.
>
> Reported-by: Justin P. Mattock<[email protected]>
> Signed-off-by: Patrick McHardy<[email protected]>
>
>
alright!! doing the above change
CONFIG_NF_CONNTRACK=y gets a clean build.. as well as reverting
everything and using your patch..
Thanks for the fix..
Justin P. Mattock
Am 18.11.2010 20:18, schrieb Justin P. Mattock:
> On 11/18/2010 10:20 AM, Patrick McHardy wrote:
>> Am 18.11.2010 19:13, schrieb Justin P. Mattock:
>>> On 11/18/2010 09:50 AM, David Miller wrote:
>>>> From: Eric Dumazet<[email protected]>
>>>> Date: Thu, 18 Nov 2010 18:48:17 +0100
>>>>
>>>>> Let me guess...
>>>>>
>>>>> net/netfilter/nf_conntrack_core is compiled as a module, and ip_vs
>>>>> statically (in vmlinux) ?
>>>>>
>>>>> CONFIG_NF_CONNTRACK=m
>>>>> CONFIG_IP_VS=y
>>>>>
>>>>> We probably need some Kconfig magic ;)
>>>>
>>
>> Please try whether this patch fixes the problem.
>>
>> netfilter: fix IP_VS dependencies
>>
>> When NF_CONNTRACK is enabled, IP_VS uses conntrack symbols.
>> Therefore IP_VS can't be linked statically when conntrack
>> is built modular.
>>
>> Reported-by: Justin P. Mattock<[email protected]>
>> Signed-off-by: Patrick McHardy<[email protected]>
>>
>>
>
>
> alright!! doing the above change
> CONFIG_NF_CONNTRACK=y gets a clean build.. as well as reverting
> everything and using your patch..
>
> Thanks for the fix..
Thanks for testing. Dave, please apply directly, thanks!
From: Patrick McHardy <[email protected]>
Date: Thu, 18 Nov 2010 21:32:11 +0100
> Thanks for testing. Dave, please apply directly, thanks!
Done.
On Thu, 18 Nov 2010 12:54:51 -0800 (PST) David Miller wrote:
> From: Patrick McHardy <[email protected]>
> Date: Thu, 18 Nov 2010 21:32:11 +0100
>
> > Thanks for testing. Dave, please apply directly, thanks!
Dave,
This patch does not fix the config/build error that I posted for linux-next.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
From: Randy Dunlap <[email protected]>
Date: Thu, 18 Nov 2010 13:03:18 -0800
> On Thu, 18 Nov 2010 12:54:51 -0800 (PST) David Miller wrote:
>
>> From: Patrick McHardy <[email protected]>
>> Date: Thu, 18 Nov 2010 21:32:11 +0100
>>
>> > Thanks for testing. Dave, please apply directly, thanks!
>
> Dave,
>
> This patch does not fix the config/build error that I posted for linux-next.
And it has bugs, now when NF_CONNTRACT is set to "m" IPVS isn't offered
at all.
So I'm reverting.
From: David Miller <[email protected]>
Date: Thu, 18 Nov 2010 13:10:04 -0800 (PST)
> From: Randy Dunlap <[email protected]>
> Date: Thu, 18 Nov 2010 13:03:18 -0800
>
>> On Thu, 18 Nov 2010 12:54:51 -0800 (PST) David Miller wrote:
>>
>>> From: Patrick McHardy <[email protected]>
>>> Date: Thu, 18 Nov 2010 21:32:11 +0100
>>>
>>> > Thanks for testing. Dave, please apply directly, thanks!
>>
>> Dave,
>>
>> This patch does not fix the config/build error that I posted for linux-next.
>
> And it has bugs, now when NF_CONNTRACT is set to "m" IPVS isn't offered
> at all.
>
> So I'm reverting.
Ignore this, I was looking for "*_IPVS" in the config instead of
"*_IP_VS" for some stupid reason.
Patch is sane and I'll look into Randy's problem when I get a chance.
:-)
Am 18.11.2010 22:15, schrieb David Miller:
> From: David Miller <[email protected]>
> Date: Thu, 18 Nov 2010 13:10:04 -0800 (PST)
>
>> From: Randy Dunlap <[email protected]>
>> Date: Thu, 18 Nov 2010 13:03:18 -0800
>>
>>> On Thu, 18 Nov 2010 12:54:51 -0800 (PST) David Miller wrote:
>>>
>>>> From: Patrick McHardy <[email protected]>
>>>> Date: Thu, 18 Nov 2010 21:32:11 +0100
>>>>
>>>>> Thanks for testing. Dave, please apply directly, thanks!
>>>
>>> Dave,
>>>
>>> This patch does not fix the config/build error that I posted for linux-next.
>>
>> And it has bugs, now when NF_CONNTRACT is set to "m" IPVS isn't offered
>> at all.
>>
>> So I'm reverting.
>
> Ignore this, I was looking for "*_IPVS" in the config instead of
> "*_IP_VS" for some stupid reason.
I always make the same mistake :)
> Patch is sane and I'll look into Randy's problem when I get a chance.
> :-)
I've already asked the tproxy guys to look into this, it's a
different problem that requires more tproxy knowledge than
have.
On 11/18/2010 01:48 PM, Patrick McHardy wrote:
> Am 18.11.2010 22:15, schrieb David Miller:
>> From: David Miller<[email protected]>
>> Date: Thu, 18 Nov 2010 13:10:04 -0800 (PST)
>>
>>> From: Randy Dunlap<[email protected]>
>>> Date: Thu, 18 Nov 2010 13:03:18 -0800
>>>
>>>> On Thu, 18 Nov 2010 12:54:51 -0800 (PST) David Miller wrote:
>>>>
>>>>> From: Patrick McHardy<[email protected]>
>>>>> Date: Thu, 18 Nov 2010 21:32:11 +0100
>>>>>
>>>>>> Thanks for testing. Dave, please apply directly, thanks!
>>>>
>>>> Dave,
>>>>
>>>> This patch does not fix the config/build error that I posted for linux-next.
>>>
>>> And it has bugs, now when NF_CONNTRACT is set to "m" IPVS isn't offered
>>> at all.
>>>
>>> So I'm reverting.
>>
>> Ignore this, I was looking for "*_IPVS" in the config instead of
>> "*_IP_VS" for some stupid reason.
>
> I always make the same mistake :)
>
>> Patch is sane and I'll look into Randy's problem when I get a chance.
>> :-)
>
> I've already asked the tproxy guys to look into this, it's a
> different problem that requires more tproxy knowledge than
> have.
>
go outside to clean the garage, and put up the christmas lights up, come
back and am freaking for a second that the problems not fixed...
tripping me out man!!
Justin P. Mattock
On Thu, Nov 18, 2010 at 03:48:00PM -0800, Justin P. Mattock wrote:
> On 11/18/2010 01:48 PM, Patrick McHardy wrote:
> >Am 18.11.2010 22:15, schrieb David Miller:
> >>From: David Miller<[email protected]>
> >>Date: Thu, 18 Nov 2010 13:10:04 -0800 (PST)
> >>
> >>>From: Randy Dunlap<[email protected]>
> >>>Date: Thu, 18 Nov 2010 13:03:18 -0800
> >>>
> >>>>On Thu, 18 Nov 2010 12:54:51 -0800 (PST) David Miller wrote:
> >>>>
> >>>>>From: Patrick McHardy<[email protected]>
> >>>>>Date: Thu, 18 Nov 2010 21:32:11 +0100
> >>>>>
> >>>>>>Thanks for testing. Dave, please apply directly, thanks!
> >>>>
> >>>>Dave,
> >>>>
> >>>>This patch does not fix the config/build error that I posted for linux-next.
> >>>
> >>>And it has bugs, now when NF_CONNTRACT is set to "m" IPVS isn't offered
> >>>at all.
> >>>
> >>>So I'm reverting.
> >>
> >>Ignore this, I was looking for "*_IPVS" in the config instead of
> >>"*_IP_VS" for some stupid reason.
> >
> >I always make the same mistake :)
> >
> >>Patch is sane and I'll look into Randy's problem when I get a chance.
> >>:-)
> >
> >I've already asked the tproxy guys to look into this, it's a
> >different problem that requires more tproxy knowledge than
> >have.
> >
>
>
> go outside to clean the garage, and put up the christmas lights up,
> come back and am freaking for a second that the problems not
> fixed...
>
> tripping me out man!!
On a similar note, sorry for not participating in the IPVS portion of
this thread, it was all over by the time that I woke up this morning.