Undefined symbols in patch for 2.6.14 kernel
Hi, I was trying to use the latest version of tproxy with the Linux kernel 2.6.14 After compilation when I try to load ip_nat module i got undefined symbols in the dmesg log: READ_LOCK READ_UNLOCK I assume the READ_LOCK can be replaced by ASSERT_READ_LOCK but could not find any similar UNLOCK defines.. Please advise. Cheers
***Compile error for READ_LOCK and READ_UNLOCK in net/ipv4/netfilter/ip_nat_core Fixed this with read_lock_bh(&ip_conntrack_lock); read_unlock_bh(&ip_conntrack_lock); On 1/4/06, Yigal Rozenberg <yigal.rozenberg@gmail.com> wrote:
Hi,
I was trying to use the latest version of tproxy with the Linux kernel 2.6.14 After compilation when I try to load ip_nat module i got undefined symbols in the dmesg log: READ_LOCK READ_UNLOCK
I assume the READ_LOCK can be replaced by ASSERT_READ_LOCK but could not find any similar UNLOCK defines.. Please advise.
Cheers _______________________________________________ tproxy mailing list tproxy@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/tproxy
Thanks, I used the same method, just wanted to be sure. Actualy it is the same way the forth patch file uses (04-nat_delete.diff). Happy new year :-) On 1/4/06, Sai Bathina <sai.bathina@gmail.com> wrote:
***Compile error for READ_LOCK and READ_UNLOCK in net/ipv4/netfilter/ip_nat_core Fixed this with read_lock_bh(&ip_conntrack_lock); read_unlock_bh(&ip_conntrack_lock);
On 1/4/06, Yigal Rozenberg <yigal.rozenberg@gmail.com> wrote:
Hi,
I was trying to use the latest version of tproxy with the Linux kernel 2.6.14 After compilation when I try to load ip_nat module i got undefined symbols in the dmesg log: READ_LOCK READ_UNLOCK
I assume the READ_LOCK can be replaced by ASSERT_READ_LOCK but could not find any similar UNLOCK defines.. Please advise.
Cheers _______________________________________________ tproxy mailing list tproxy@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/tproxy
participants (2)
-
Sai Bathina
-
Yigal Rozenberg