possible deadlock in xt_find_revision

6 views
Skip to first unread message

syzbot

unread,
Jan 6, 2020, 3:11:20 PM1/6/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 84f5ad46 Linux 4.14.162
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14c14656e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=67bcc84091a71c98
dashboard link: https://syzkaller.appspot.com/bug?extid=ed933a328f896a227a7a
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+ed933a...@syzkaller.appspotmail.com

======================================================
WARNING: possible circular locking dependency detected
4.14.162-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.3/32389 is trying to acquire lock:
(&xt[i].mutex){+.+.}, at: [<ffffffff854e6002>] xt_find_revision+0x82/0x200
net/netfilter/x_tables.c:373

but task is already holding lock:
(&table[i].mutex){+.+.}, at: [<ffffffff8541140a>] nfnl_lock
net/netfilter/nfnetlink.c:61 [inline]
(&table[i].mutex){+.+.}, at: [<ffffffff8541140a>]
nfnetlink_rcv_msg+0x78a/0xc00 net/netfilter/nfnetlink.c:209

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&table[i].mutex){+.+.}:
lock_acquire+0x16f/0x430 kernel/locking/lockdep.c:3994
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xe8/0x1470 kernel/locking/mutex.c:893
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:908
nfnl_lock+0x24/0x30 net/netfilter/nfnetlink.c:61
nf_tables_netdev_event+0x13f/0x580
net/netfilter/nf_tables_netdev.c:122
notifier_call_chain+0x111/0x1b0 kernel/notifier.c:93
__raw_notifier_call_chain kernel/notifier.c:394 [inline]
raw_notifier_call_chain+0x2e/0x40 kernel/notifier.c:401
call_netdevice_notifiers_info+0x56/0x70 net/core/dev.c:1671
call_netdevice_notifiers net/core/dev.c:1687 [inline]
rollback_registered_many+0x70d/0xb60 net/core/dev.c:7214
unregister_netdevice_many.part.0+0x1b/0x1e0 net/core/dev.c:8268
unregister_netdevice_many+0x3b/0x50 net/core/dev.c:8267
ip6gre_exit_net+0x3fe/0x5a0 net/ipv6/ip6_gre.c:1208
ops_exit_list.isra.0+0xaa/0x150 net/core/net_namespace.c:142
cleanup_net+0x3ba/0x870 net/core/net_namespace.c:484
process_one_work+0x863/0x1600 kernel/workqueue.c:2114
worker_thread+0x5d9/0x1050 kernel/workqueue.c:2248
kthread+0x319/0x430 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404

-> #1 (rtnl_mutex){+.+.}:
lock_acquire+0x16f/0x430 kernel/locking/lockdep.c:3994
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xe8/0x1470 kernel/locking/mutex.c:893
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:908
rtnl_lock+0x17/0x20 net/core/rtnetlink.c:72
unregister_netdevice_notifier+0x5f/0x2c0 net/core/dev.c:1634
tee_tg_destroy+0x61/0xc0 net/netfilter/xt_TEE.c:123
cleanup_entry+0x1a6/0x260 net/ipv6/netfilter/ip6_tables.c:684
__do_replace+0x3c5/0x5c0 net/ipv6/netfilter/ip6_tables.c:1105
do_replace net/ipv6/netfilter/ip6_tables.c:1161 [inline]
do_ip6t_set_ctl+0x296/0x3f4 net/ipv6/netfilter/ip6_tables.c:1685
nf_sockopt net/netfilter/nf_sockopt.c:106 [inline]
nf_setsockopt+0x67/0xc0 net/netfilter/nf_sockopt.c:115
ipv6_setsockopt net/ipv6/ipv6_sockglue.c:930 [inline]
ipv6_setsockopt+0x105/0x130 net/ipv6/ipv6_sockglue.c:914
udpv6_setsockopt+0x4e/0x90 net/ipv6/udp.c:1459
sock_common_setsockopt+0x94/0xd0 net/core/sock.c:2968
SYSC_setsockopt net/socket.c:1865 [inline]
SyS_setsockopt+0x13c/0x210 net/socket.c:1844
do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7

-> #0 (&xt[i].mutex){+.+.}:
check_prev_add kernel/locking/lockdep.c:1901 [inline]
check_prevs_add kernel/locking/lockdep.c:2018 [inline]
validate_chain kernel/locking/lockdep.c:2460 [inline]
__lock_acquire+0x2cb3/0x4620 kernel/locking/lockdep.c:3487
lock_acquire+0x16f/0x430 kernel/locking/lockdep.c:3994
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xe8/0x1470 kernel/locking/mutex.c:893
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:908
xt_find_revision+0x82/0x200 net/netfilter/x_tables.c:373
nfnl_compat_get+0x229/0x950 net/netfilter/nft_compat.c:678
nfnetlink_rcv_msg+0xa08/0xc00 net/netfilter/nfnetlink.c:214
netlink_rcv_skb+0x14f/0x3c0 net/netlink/af_netlink.c:2432
nfnetlink_rcv+0x1ab/0x1650 net/netfilter/nfnetlink.c:515
netlink_unicast_kernel net/netlink/af_netlink.c:1286 [inline]
netlink_unicast+0x44d/0x650 net/netlink/af_netlink.c:1312
netlink_sendmsg+0x7c4/0xc60 net/netlink/af_netlink.c:1877
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xce/0x110 net/socket.c:656
___sys_sendmsg+0x70a/0x840 net/socket.c:2062
__sys_sendmsg+0xb9/0x140 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x2d/0x50 net/socket.c:2103
do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7

other info that might help us debug this:

Chain exists of:
&xt[i].mutex --> rtnl_mutex --> &table[i].mutex

Possible unsafe locking scenario:

CPU0 CPU1
---- ----
lock(&table[i].mutex);
lock(rtnl_mutex);
lock(&table[i].mutex);
lock(&xt[i].mutex);

*** DEADLOCK ***

1 lock held by syz-executor.3/32389:
#0: (&table[i].mutex){+.+.}, at: [<ffffffff8541140a>] nfnl_lock
net/netfilter/nfnetlink.c:61 [inline]
#0: (&table[i].mutex){+.+.}, at: [<ffffffff8541140a>]
nfnetlink_rcv_msg+0x78a/0xc00 net/netfilter/nfnetlink.c:209

stack backtrace:
CPU: 0 PID: 32389 Comm: syz-executor.3 Not tainted 4.14.162-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x142/0x197 lib/dump_stack.c:58
print_circular_bug.isra.0.cold+0x1cc/0x28f kernel/locking/lockdep.c:1258
check_prev_add kernel/locking/lockdep.c:1901 [inline]
check_prevs_add kernel/locking/lockdep.c:2018 [inline]
validate_chain kernel/locking/lockdep.c:2460 [inline]
__lock_acquire+0x2cb3/0x4620 kernel/locking/lockdep.c:3487
lock_acquire+0x16f/0x430 kernel/locking/lockdep.c:3994
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xe8/0x1470 kernel/locking/mutex.c:893
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:908
xt_find_revision+0x82/0x200 net/netfilter/x_tables.c:373
nfnl_compat_get+0x229/0x950 net/netfilter/nft_compat.c:678
nfnetlink_rcv_msg+0xa08/0xc00 net/netfilter/nfnetlink.c:214
netlink_rcv_skb+0x14f/0x3c0 net/netlink/af_netlink.c:2432
nfnetlink_rcv+0x1ab/0x1650 net/netfilter/nfnetlink.c:515
netlink_unicast_kernel net/netlink/af_netlink.c:1286 [inline]
netlink_unicast+0x44d/0x650 net/netlink/af_netlink.c:1312
netlink_sendmsg+0x7c4/0xc60 net/netlink/af_netlink.c:1877
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xce/0x110 net/socket.c:656
___sys_sendmsg+0x70a/0x840 net/socket.c:2062
__sys_sendmsg+0xb9/0x140 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x2d/0x50 net/socket.c:2103
do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45af49
RSP: 002b:00007f230572bc78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045af49
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000003
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f230572c6d4
R13: 00000000004c9fec R14: 00000000004e2e30 R15: 00000000ffffffff
overlayfs: workdir and upperdir must be separate subtrees
netlink: 16 bytes leftover after parsing attributes in process
`syz-executor.5'.
netlink: 16 bytes leftover after parsing attributes in process
`syz-executor.5'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.3'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.3'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.5'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.2'.
selinux_nlmsg_perm: 593 callbacks suppressed
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0
sclass=netlink_route_socket pig=32536 comm=syz-executor.2
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0
sclass=netlink_route_socket pig=32536 comm=syz-executor.2
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0
sclass=netlink_route_socket pig=32545 comm=syz-executor.4
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0
sclass=netlink_route_socket pig=32536 comm=syz-executor.2
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.4'.
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0
sclass=netlink_route_socket pig=32536 comm=syz-executor.2
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0
sclass=netlink_route_socket pig=32536 comm=syz-executor.2
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0
sclass=netlink_route_socket pig=32545 comm=syz-executor.4
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0
sclass=netlink_route_socket pig=32536 comm=syz-executor.2
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0
sclass=netlink_route_socket pig=32545 comm=syz-executor.4
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0
sclass=netlink_route_socket pig=32536 comm=syz-executor.2
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.1'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.3'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.5'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.2'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.4'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.3'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.1'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.5'.
netlink: 2220 bytes leftover after parsing attributes in process
`syz-executor.2'.
Cannot find add_set index 0 as target
Cannot find add_set index 0 as target
Cannot find add_set index 0 as target
SELinux: security_context_str_to_sid(sysadm_u) failed for (dev bpf, type
bpf) errno=-22
SELinux: security_context_str_to_sid(sysadm_u) failed for (dev bpf, type
bpf) errno=-22
SELinux: security_context_str_to_sid(sysadm_u) failed for (dev bpf, type
bpf) errno=-22
Cannot find add_set index 0 as target
Cannot find add_set index 0 as target
SELinux: security_context_str_to_sid(sysadm_u) failed for (dev bpf, type
bpf) errno=-22
SELinux: security_context_str_to_sid(sysadm_u) failed for (dev bpf, type
bpf) errno=-22
SELinux: security_context_str_to_sid(sysadm_u) failed for (dev bpf, type
bpf) errno=-22
SELinux: security_context_str_to_sid(sysadm_u) failed for (dev bpf, type
bpf) errno=-22


---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Sep 2, 2020, 10:09:22 PM9/2/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: d7e78d08 Linux 4.14.195
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12a06cf5900000
kernel config: https://syzkaller.appspot.com/x/.config?x=6608b656f49b4e8c
dashboard link: https://syzkaller.appspot.com/bug?extid=ed933a328f896a227a7a
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12c09115900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1108d6c1900000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ed933a...@syzkaller.appspotmail.com

ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
======================================================
WARNING: possible circular locking dependency detected
4.14.195-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor412/6569 is trying to acquire lock:
(&xt[i].mutex){+.+.}, at: [<ffffffff85407908>] xt_find_revision+0x88/0x200 net/netfilter/x_tables.c:373

but task is already holding lock:
(&table[i].mutex){+.+.}, at: [<ffffffff85337306>] nfnl_lock net/netfilter/nfnetlink.c:61 [inline]
(&table[i].mutex){+.+.}, at: [<ffffffff85337306>] nfnetlink_rcv_msg+0x726/0xc00 net/netfilter/nfnetlink.c:209

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&table[i].mutex){+.+.}:
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
nf_tables_netdev_event+0x10d/0x4d0 net/netfilter/nf_tables_netdev.c:122
notifier_call_chain+0x108/0x1a0 kernel/notifier.c:93
call_netdevice_notifiers_info net/core/dev.c:1667 [inline]
call_netdevice_notifiers net/core/dev.c:1683 [inline]
rollback_registered_many+0x70b/0xb30 net/core/dev.c:7202
unregister_netdevice_many.part.0+0x18/0x2e0 net/core/dev.c:8284
unregister_netdevice_many+0x36/0x50 net/core/dev.c:8283
ip6gre_exit_net+0x41e/0x570 net/ipv6/ip6_gre.c:1212
ops_exit_list+0xa5/0x150 net/core/net_namespace.c:142
cleanup_net+0x3b3/0x840 net/core/net_namespace.c:484
process_one_work+0x793/0x14a0 kernel/workqueue.c:2116
worker_thread+0x5cc/0xff0 kernel/workqueue.c:2250
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404

-> #1 (rtnl_mutex){+.+.}:
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
unregister_netdevice_notifier+0x5e/0x2b0 net/core/dev.c:1630
tee_tg_destroy+0x5c/0xb0 net/netfilter/xt_TEE.c:123
cleanup_entry+0x1fd/0x2d0 net/ipv4/netfilter/ip_tables.c:666
__do_replace+0x38d/0x570 net/ipv4/netfilter/ip_tables.c:1086
do_replace net/ipv4/netfilter/ip_tables.c:1142 [inline]
do_ipt_set_ctl+0x256/0x39e net/ipv4/netfilter/ip_tables.c:1674
nf_sockopt net/netfilter/nf_sockopt.c:106 [inline]
nf_setsockopt+0x5f/0xb0 net/netfilter/nf_sockopt.c:115
ip_setsockopt net/ipv4/ip_sockglue.c:1255 [inline]
ip_setsockopt+0x94/0xb0 net/ipv4/ip_sockglue.c:1240
udp_setsockopt+0x45/0x80 net/ipv4/udp.c:2451
SYSC_setsockopt net/socket.c:1865 [inline]
SyS_setsockopt+0x110/0x1e0 net/socket.c:1844
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb

-> #0 (&xt[i].mutex){+.+.}:
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
xt_find_revision+0x88/0x200 net/netfilter/x_tables.c:373
nfnl_compat_get+0x1f7/0x870 net/netfilter/nft_compat.c:678
nfnetlink_rcv_msg+0x9bb/0xc00 net/netfilter/nfnetlink.c:214
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2433
nfnetlink_rcv+0x1ab/0x1da0 net/netfilter/nfnetlink.c:515
netlink_unicast_kernel net/netlink/af_netlink.c:1287 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1313
netlink_sendmsg+0x62e/0xb80 net/netlink/af_netlink.c:1878
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb

other info that might help us debug this:

Chain exists of:
&xt[i].mutex --> rtnl_mutex --> &table[i].mutex

Possible unsafe locking scenario:

CPU0 CPU1
---- ----
lock(&table[i].mutex);
lock(rtnl_mutex);
lock(&table[i].mutex);
lock(&xt[i].mutex);

*** DEADLOCK ***

1 lock held by syz-executor412/6569:
#0: (&table[i].mutex){+.+.}, at: [<ffffffff85337306>] nfnl_lock net/netfilter/nfnetlink.c:61 [inline]
#0: (&table[i].mutex){+.+.}, at: [<ffffffff85337306>] nfnetlink_rcv_msg+0x726/0xc00 net/netfilter/nfnetlink.c:209

stack backtrace:
CPU: 0 PID: 6569 Comm: syz-executor412 Not tainted 4.14.195-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258
check_prev_add kernel/locking/lockdep.c:1905 [inline]
check_prevs_add kernel/locking/lockdep.c:2022 [inline]
validate_chain kernel/locking/lockdep.c:2464 [inline]
__lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__mutex_lock_common kernel/locking/mutex.c:756 [inline]
__mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893
xt_find_revision+0x88/0x200 net/netfilter/x_tables.c:373
nfnl_compat_get+0x1f7/0x870 net/netfilter/nft_compat.c:678
nfnetlink_rcv_msg+0x9bb/0xc00 net/netfilter/nfnetlink.c:214
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2433
nfnetlink_rcv+0x1ab/0x1da0 net/netfilter/nfnetlink.c:515
netlink_unicast_kernel net/netlink/af_netlink.c:1287 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1313
netlink_sendmsg+0x62e/0xb80 net/netlink/af_netlink.c:1878
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x441dd9
RSP: 002b:00007ffc84d94038 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000441dd9
RDX: 0000000000000000 RSI: 0000000020000100 RDI: 0000000000000004
RBP: 000000000000d785 R08: 0000000b004002c8 R09: 0000000b004002c8
R10: 0000000b004002c8 R11: 0000000000000246 R12: 0000000000402b80
R13: 0000000000402c10 R14: 0000000000000000 R15: 0000000000000000
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table
IPVS: ftp: loaded support on port[0] = 21
ip_tables: iptables: counters copy to user failed while replacing table

Reply all
Reply to author
Forward
0 new messages