Liu Jian
d900f3d20c
bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser()
When the buffer length of the recvmsg system call is 0, we got the
flollowing soft lockup problem:
watchdog: BUG: soft lockup - CPU#3 stuck for 27s! [a.out:6149]
CPU: 3 PID: 6149 Comm: a.out Kdump: loaded Not tainted 6.2.0+ #30
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
RIP: 0010:remove_wait_queue+0xb/0xc0
Code: 5e 41 5f c3 cc cc cc cc 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 57 <41> 56 41 55 41 54 55 48 89 fd 53 48 89 f3 4c 8d 6b 18 4c 8d 73 20
RSP: 0018:ffff88811b5978b8 EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffff88811a7d3780 RCX: ffffffffb7a4d768
RDX: dffffc0000000000 RSI: ffff88811b597908 RDI: ffff888115408040
RBP: 1ffff110236b2f1b R08: 0000000000000000 R09: ffff88811a7d37e7
R10: ffffed10234fa6fc R11: 0000000000000001 R12: ffff88811179b800
R13: 0000000000000001 R14: ffff88811a7d38a8 R15: ffff88811a7d37e0
FS: 00007f6fb5398740(0000) GS:ffff888237180000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000000 CR3: 000000010b6ba002 CR4: 0000000000370ee0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
tcp_msg_wait_data+0x279/0x2f0
tcp_bpf_recvmsg_parser+0x3c6/0x490
inet_recvmsg+0x280/0x290
sock_recvmsg+0xfc/0x120
____sys_recvmsg+0x160/0x3d0
___sys_recvmsg+0xf0/0x180
__sys_recvmsg+0xea/0x1a0
do_syscall_64+0x3f/0x90
entry_SYSCALL_64_after_hwframe+0x72/0xdc
The logic in tcp_bpf_recvmsg_parser is as follows:
msg_bytes_ready:
copied = sk_msg_recvmsg(sk, psock, msg, len, flags);
if (!copied) {
wait data;
goto msg_bytes_ready;
}
In this case, "copied" always is 0, the infinite loop occurs.
According to the Linux system call man page, 0 should be returned in this
case. Therefore, in tcp_bpf_recvmsg_parser(), if the length is 0, directly
return. Also modify several other functions with the same problem.
Fixes: 1f5be6b3b0 ("udp: Implement udp_bpf_recvmsg() for sockmap")
Fixes: 9825d866ce ("af_unix: Implement unix_dgram_bpf_recvmsg()")
Fixes: c5d2177a72 ("bpf, sockmap: Fix race in ingress receive verdict with redirect to self")
Fixes: 604326b41a ("bpf, sockmap: convert to generic sk_msg interface")
Signed-off-by: Liu Jian <liujian56@huawei.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: John Fastabend <john.fastabend@gmail.com>
Cc: Jakub Sitnicki <jakub@cloudflare.com>
Link: https://lore.kernel.org/bpf/20230303080946.1146638-1-liujian56@huawei.com
2023-03-03 17:25:15 +01:00
..
2023-02-22 21:25:23 -08:00
2023-02-15 10:25:21 +00:00
2023-02-13 18:35:15 +08:00
2022-08-22 17:59:37 -07:00
2023-01-25 10:25:57 -08:00
2023-02-01 20:54:27 -08:00
2022-10-20 17:24:59 -07:00
2022-11-30 13:17:52 -08:00
2022-10-19 09:00:53 +02:00
2023-02-13 18:35:15 +08:00
2022-12-06 20:34:43 -08:00
2022-02-17 11:44:20 -08:00
2021-09-28 17:32:56 -07:00
2022-04-30 15:12:58 +01:00
2023-01-23 21:37:39 -08:00
2022-11-22 20:18:20 -08:00
2023-01-24 10:58:11 +01:00
2023-01-24 10:58:11 +01:00
2023-01-24 10:58:11 +01:00
2021-05-17 15:29:35 -07:00
2022-08-25 10:33:21 +02:00
2023-01-26 10:52:18 +01:00
2022-11-18 02:15:15 +01:00
2023-02-20 16:31:49 -08:00
2022-05-12 16:52:18 -07:00
2022-10-31 20:14:27 -07:00
2023-01-25 22:45:00 -08:00
2023-02-15 10:25:21 +00:00
2022-07-08 12:10:33 +01:00
2022-07-15 11:49:55 +01:00
2022-10-31 20:14:27 -07:00
2022-12-08 18:19:59 -08:00
2023-02-01 20:54:27 -08:00
2022-01-29 17:53:07 +00:00
2023-02-01 20:54:27 -08:00
2023-01-25 22:45:00 -08:00
2022-10-03 07:59:06 +01:00
2022-11-16 12:48:44 +00:00
2022-11-16 12:48:44 +00:00
2022-09-29 07:18:00 +02:00
2022-08-04 11:31:20 -07:00
2022-11-16 12:48:44 +00:00
2022-06-24 11:34:38 +01:00
2022-12-25 13:38:09 -08:00
2022-11-16 13:02:04 +00:00
2023-01-24 10:58:11 +01:00
2023-01-23 21:37:25 -08:00
2022-05-16 13:03:29 +02:00
2022-10-27 10:17:40 -07:00
2022-12-08 18:19:59 -08:00
2023-01-26 10:52:18 +01:00
2021-05-17 15:29:35 -07:00
2022-06-21 11:38:29 +02:00
2023-02-03 19:56:23 -08:00
2022-11-18 02:15:15 +01:00
2022-12-12 13:11:24 -08:00
2022-11-16 09:43:35 +00:00
2023-02-02 00:25:14 +01:00
2022-04-06 12:05:41 -07:00
2023-03-03 17:25:15 +01:00
2022-10-16 15:27:07 -07:00
2023-02-02 00:25:14 +01:00
2023-02-02 00:25:14 +01:00
2023-02-02 00:25:14 +01:00
2022-09-20 10:21:49 -07:00
2022-08-17 10:19:22 +01:00
2022-04-06 12:05:41 -07:00
2022-04-06 12:05:41 -07:00
2022-04-06 12:05:41 -07:00
2022-04-06 12:05:41 -07:00
2022-12-13 15:47:48 -08:00
2023-02-02 21:14:50 -08:00
2022-04-06 12:05:41 -07:00
2022-08-29 12:47:15 +01:00
2023-02-27 11:59:29 -08:00
2022-04-06 12:05:41 -07:00
2022-10-03 12:38:34 +01:00
2022-12-01 15:53:05 -08:00
2022-12-20 03:13:45 +01:00
2022-04-28 13:02:01 -07:00
2022-07-20 10:14:50 +01:00
2022-04-06 12:05:41 -07:00
2022-08-17 10:19:22 +01:00
2023-01-19 09:26:16 -08:00
2022-04-06 12:05:41 -07:00
2022-04-06 12:05:41 -07:00
2022-04-06 12:05:41 -07:00
2022-04-06 12:05:41 -07:00
2023-01-20 13:23:35 +00:00
2021-05-17 15:29:35 -07:00
2023-03-03 17:25:15 +01:00
2022-11-16 09:43:35 +00:00
2022-04-12 15:00:25 +02:00
2022-12-12 09:29:56 +00:00
2022-12-12 09:51:52 +00:00
2022-11-29 08:44:24 -08:00
2023-01-25 22:45:00 -08:00
2022-10-12 17:50:37 -07:00
2022-06-09 21:52:55 -07:00
2022-06-08 10:10:13 -07:00
2022-09-29 07:18:00 +02:00