Wang Liang
073d89808c
net: fix data-races around sk->sk_forward_alloc
Syzkaller reported this warning:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 16 at net/ipv4/af_inet.c:156 inet_sock_destruct+0x1c5/0x1e0
Modules linked in:
CPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.12.0-rc5 #26
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
RIP: 0010:inet_sock_destruct+0x1c5/0x1e0
Code: 24 12 4c 89 e2 5b 48 c7 c7 98 ec bb 82 41 5c e9 d1 18 17 ff 4c 89 e6 5b 48 c7 c7 d0 ec bb 82 41 5c e9 bf 18 17 ff 0f 0b eb 83 <0f> 0b eb 97 0f 0b eb 87 0f 0b e9 68 ff ff ff 66 66 2e 0f 1f 84 00
RSP: 0018:ffffc9000008bd90 EFLAGS: 00010206
RAX: 0000000000000300 RBX: ffff88810b172a90 RCX: 0000000000000007
RDX: 0000000000000002 RSI: 0000000000000300 RDI: ffff88810b172a00
RBP: ffff88810b172a00 R08: ffff888104273c00 R09: 0000000000100007
R10: 0000000000020000 R11: 0000000000000006 R12: ffff88810b172a00
R13: 0000000000000004 R14: 0000000000000000 R15: ffff888237c31f78
FS: 0000000000000000(0000) GS:ffff888237c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc63fecac8 CR3: 000000000342e000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
? __warn+0x88/0x130
? inet_sock_destruct+0x1c5/0x1e0
? report_bug+0x18e/0x1a0
? handle_bug+0x53/0x90
? exc_invalid_op+0x18/0x70
? asm_exc_invalid_op+0x1a/0x20
? inet_sock_destruct+0x1c5/0x1e0
__sk_destruct+0x2a/0x200
rcu_do_batch+0x1aa/0x530
? rcu_do_batch+0x13b/0x530
rcu_core+0x159/0x2f0
handle_softirqs+0xd3/0x2b0
? __pfx_smpboot_thread_fn+0x10/0x10
run_ksoftirqd+0x25/0x30
smpboot_thread_fn+0xdd/0x1d0
kthread+0xd3/0x100
? __pfx_kthread+0x10/0x10
ret_from_fork+0x34/0x50
? __pfx_kthread+0x10/0x10
ret_from_fork_asm+0x1a/0x30
</TASK>
---[ end trace 0000000000000000 ]---
Its possible that two threads call tcp_v6_do_rcv()/sk_forward_alloc_add()
concurrently when sk->sk_state == TCP_LISTEN with sk->sk_lock unlocked,
which triggers a data-race around sk->sk_forward_alloc:
tcp_v6_rcv
tcp_v6_do_rcv
skb_clone_and_charge_r
sk_rmem_schedule
__sk_mem_schedule
sk_forward_alloc_add()
skb_set_owner_r
sk_mem_charge
sk_forward_alloc_add()
__kfree_skb
skb_release_all
skb_release_head_state
sock_rfree
sk_mem_uncharge
sk_forward_alloc_add()
sk_mem_reclaim
// set local var reclaimable
__sk_mem_reclaim
sk_forward_alloc_add()
In this syzkaller testcase, two threads call
tcp_v6_do_rcv() with skb->truesize=768, the sk_forward_alloc changes like
this:
(cpu 1) | (cpu 2) | sk_forward_alloc
... | ... | 0
__sk_mem_schedule() | | +4096 = 4096
| __sk_mem_schedule() | +4096 = 8192
sk_mem_charge() | | -768 = 7424
| sk_mem_charge() | -768 = 6656
... | ... |
sk_mem_uncharge() | | +768 = 7424
reclaimable=7424 | |
| sk_mem_uncharge() | +768 = 8192
| reclaimable=8192 |
__sk_mem_reclaim() | | -4096 = 4096
| __sk_mem_reclaim() | -8192 = -4096 != 0
The skb_clone_and_charge_r() should not be called in tcp_v6_do_rcv() when
sk->sk_state is TCP_LISTEN, it happens later in tcp_v6_syn_recv_sock().
Fix the same issue in dccp_v6_do_rcv().
Suggested-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Fixes: e994b2f0fb ("tcp: do not lock listener to process SYN packets")
Signed-off-by: Wang Liang <wangliang74@huawei.com>
Link: https://patch.msgid.link/20241107023405.889239-1-wangliang74@huawei.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2024-11-11 15:29:33 -08:00
..
2024-09-05 14:57:12 -07:00
2024-10-30 13:17:36 +01:00
2024-01-30 12:43:18 +01:00
2024-10-02 17:23:23 -04:00
2024-04-08 11:01:05 +01:00
2024-08-29 13:00:36 -07:00
2024-02-09 14:12:01 -08:00
2024-05-01 11:46:21 +01:00
2024-10-02 17:23:23 -04:00
2023-12-11 10:59:17 +00:00
2024-06-17 13:53:19 +02:00
2024-09-11 20:44:31 -07:00
2023-05-24 08:43:39 +01:00
2024-01-05 08:11:49 -08:00
2024-03-11 15:15:08 -07:00
2024-09-13 21:15:45 -07:00
2024-08-30 11:14:06 -07:00
2023-10-01 19:09:54 +01:00
2024-08-05 16:27:26 -07:00
2024-09-03 11:38:32 -07:00
2024-03-01 08:42:33 +00:00
2024-06-20 13:49:59 -07:00
2023-09-15 10:33:48 +01:00
2024-09-03 11:36:43 +02:00
2024-09-06 18:10:21 -07:00
2024-05-27 16:46:59 -07:00
2024-08-21 17:35:49 -07:00
2024-09-04 16:57:11 -07:00
2024-02-09 14:12:01 -08:00
2024-05-07 16:19:14 -07:00
2024-09-03 11:36:43 +02:00
2022-09-29 07:18:00 +02:00
2024-08-26 14:53:50 -07:00
2024-09-22 19:52:07 +01:00
2023-10-27 10:35:44 +01:00
2021-04-27 14:02:06 -07:00
2024-08-26 09:48:53 -07:00
2024-02-09 14:12:01 -08:00
2024-08-29 12:33:07 -07:00
2024-06-13 13:13:46 -07:00
2024-03-01 08:42:31 +00:00
2024-04-29 13:32:01 +01:00
2024-07-28 13:41:14 -07:00
2024-06-19 12:44:22 +01:00
2024-05-23 14:14:23 -07:00
2024-09-15 09:13:19 -07:00
2024-09-13 19:55:49 -07:00
2023-06-19 11:32:58 -07:00
2024-05-21 13:16:25 +02:00
2024-06-03 18:50:08 -07:00
2024-06-24 16:41:23 -07:00
2024-05-30 18:29:38 -07:00
2024-09-04 16:57:11 -07:00
2024-06-19 12:44:22 +01:00
2024-07-24 20:59:29 +02:00
2023-10-27 10:35:46 +01:00
2024-11-11 15:29:33 -08:00
2024-10-02 17:21:47 -07:00
2024-02-09 14:12:01 -08:00
2022-10-12 17:50:37 -07:00
2024-05-02 11:02:48 +02:00
2024-10-15 18:12:33 -07:00
2023-09-14 16:16:36 +02:00
2024-05-09 10:01:01 -07:00
2023-10-25 18:04:29 -07:00
2024-09-23 07:02:07 +02:00
2024-03-08 10:56:05 +00:00