search for: fib_frontend

...o build my kernel. Any ideas? Thanks! gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -fno-unit-at-a-time -nostdinc -iwithprefix include -DKBUILD_BASENAME=fib_frontend -c -o fib_frontend.o fib_frontend.c fib_frontend.c: In function `fib_validate_source'': /usr/src/linux/include/net/ip_fib.h:178: sorry, unimplemented: inlining failed in call to ''fib_result_table'': function body not available fib_frontend.c:253: sorry, unimplemented: call...

I am using kernel 2.6.9 (gentoo,AMD64 version) + routes-2.6.9-11.diff If compile kernel with gcc 3.4.3, then the similar error comes out: ------------------ net/ipv4/fib_frontend.c: In function `fib_validate_source'': include/net/ip_fib.h:181: sorry, unimplemented: inlining failed in call to ''fib_result_table'': function body not available net/ipv4/fib_frontend.c:204: sorry, unimplemented: called from here include/net/ip_fib.h:181: sorry, unimpleme...

Dear Sir, Please help me in building the right solution. My requirement is: 1st I want to club both ISP bandwidth to get 512kbps. 2nd, In normal condition, it should be in Load balancing. 3rd , In ISP Failover condition, traffic will automatically route to working ISP. What I have: I have installed the RHEL 3.0 with 3 Network Card. Kernel is 2.4.21-9EL I have the link from two ISP both

...it happen before NF_IP_PRE_ROUTING (PREROUTING) or not? Does it only happen at route selection time? What I have tried to do to find the answer: - - - - - - - - - - - - - - - - - - - - - - I find a posting (from many years ago) [0], which suggests that this happens in fib_validate_source() (in fib_frontend.c) which is only called by route.c. I tried following the diagram by Mathieu Lafon to see if fib_validate_source() is called in ip_rcv() (in ip_input.c), but I don''t read C very well, so I could well be missing where the rp_filter validation is occurring. If I understand the path correct...

...Hunk #1 FAILED at 49. >> Hunk #2 succeeded at 120 with fuzz 2 (offset -8 lines). >> Hunk #3 FAILED at 140. >> 2 out of 3 hunks FAILED -- saving rejects to file >> linux/include/net/route.h.rej >> patching file linux/net/ipv4/arp.c >> patching file linux/net/ipv4/fib_frontend.c >> Hunk #3 succeeded at 212 with fuzz 2. >> Hunk #4 FAILED at 222. >> Hunk #5 FAILED at 244. > > The Red Hat kernels are not just plain vanilla kernels. They already > have a number of patches applied by Red Hat and it is likely that the > patch being applied by you...

...f patching file include/linux/netfilter_ipv4/ip_nat.h patching file include/linux/rtnetlink.h patching file include/net/ip_fib.h patching file include/net/route.h Hunk #2 succeeded at 130 (offset 2 lines). patching file net/ipv4/arp.c Hunk #1 succeeded at 317 (offset 1 line). patching file net/ipv4/fib_frontend.c patching file net/ipv4/fib_hash.c Hunk #2 succeeded at 337 (offset 24 lines). Hunk #4 succeeded at 489 (offset 24 lines). Hunk #5 succeeded at 629 (offset -2 lines). patching file net/ipv4/fib_rules.c patching file net/ipv4/fib_semantics.c Hunk #4 succeeded at 366 with fuzz 2. Hunk #5 FAILED at 3...

...ridges/vme_tsi148.c: function tsi148_slave_set line 38 drivers/vme/bridges/vme_tsi148.c: function tsi148_dma_set_vme_dest_attributes line 87 drivers/vme/bridges/vme_tsi148.c: function tsi148_dma_set_vme_src_attributes line 87 drivers/vme/bridges/vme_tsi148.c: function tsi148_lm_set line 41 net/ipv4/fib_frontend.c: function fib_gw_from_via line 35 arch/arm/mach-s3c/mach-rx1950.c: function rx1950_led_blink_set line 17 tools/perf/ui/stdio/hist.c: function hist_entry_callchain__fprintf line 15 tools/perf/ui/stdio/hist.c: function hist_entry_callchain__fprintf line 21 tools/perf/ui/stdio/hist.c: function hist_...

...ridges/vme_tsi148.c: function tsi148_slave_set line 38 drivers/vme/bridges/vme_tsi148.c: function tsi148_dma_set_vme_dest_attributes line 87 drivers/vme/bridges/vme_tsi148.c: function tsi148_dma_set_vme_src_attributes line 87 drivers/vme/bridges/vme_tsi148.c: function tsi148_lm_set line 41 net/ipv4/fib_frontend.c: function fib_gw_from_via line 35 arch/arm/mach-s3c/mach-rx1950.c: function rx1950_led_blink_set line 17 tools/perf/ui/stdio/hist.c: function hist_entry_callchain__fprintf line 15 tools/perf/ui/stdio/hist.c: function hist_entry_callchain__fprintf line 21 tools/perf/ui/stdio/hist.c: function hist_...

From: Tom Rix <trix at redhat.com> This is a upcoming change to clean up a new warning treewide. I am wondering if the change could be one mega patch (see below) or normal patch per file about 100 patches or somewhere half way by collecting early acks. clang has a number of useful, new warnings see

From: Tom Rix <trix at redhat.com> This is a upcoming change to clean up a new warning treewide. I am wondering if the change could be one mega patch (see below) or normal patch per file about 100 patches or somewhere half way by collecting early acks. clang has a number of useful, new warnings see

Hi All, I followed the instructions here at http://bderzhavets.wordpress.com/2009/06/10/setup-fedora-11-pv-domu-at-xen-3-4-1-dom0-kernel-2-6-30-rc6-tip-on-top-of-fedora-11/ However, when I do a "make menuconfig", I cannot see any XEN related configuration options. What am I missing? Thank you. Mr. Teo En Ming Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)