Re: possible deadlock in raw_setsockopt

From: Yikebaer Aizezi
Date: Sat Aug 12 2023 - 10:08:30 EST

Next message: Konrad Dybcio: "Re: [PATCH 2/2] ARM: dts: qcom: ipq4019-ap.dk01.1: align flash node with bindings"
Previous message: Robert Marko: "Re: [PATCH 2/2] ARM: dts: qcom: ipq4019-ap.dk01.1: align flash node with bindings"
In reply to: Oliver Hartkopp: "Re: possible deadlock in raw_setsockopt"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Thanks, I'll check it out.

Oliver Hartkopp <socketcan@xxxxxxxxxxxx> 于2023年8月12日周六 19:44写道：
>
> Hello,
>
> it seems to be the common pattern to use
>
> rtnl_lock();
> lock_sock(sk);
>
> (..)
>
> release_lock(sk);
> rtnl_unlock();
>
> And the referenced code here
> home/smyl/linux-image/linux-6.5-rc3/net/can/raw.c:607
> already follows this pattern.
>
> A wrong locking has been introduced in
>
> ee8b94c8510c ("can: raw: fix receiver memory leak")
>
> which has been fixed in
>
> 11c9027c983e ("can: raw: fix lockdep issue in raw_release()")
>
> Your selected linux-6.5-rc3 tree has the above problem but it is fixed
> in Linus' latest tree now.
>
> Best regards,
> Oliver
>
> On 10.08.23 12:30, Yikebaer Aizezi wrote:
> > Hello,
> >
> > When using Healer to fuzz the Linux-6.5-rc3, the following crash
> > was triggered.
> >
> > HEAD commit: 6eaae198076080886b9e7d57f4ae06fa782f90ef (tag: v6.5-rc3)
> > git tree: upstream
> > console output:
> > https://drive.google.com/file/d/1d9rLH0SYwNhTm2datRKbVpET1irbx_tA/view?usp=drive_link
> > kernel config: https://drive.google.com/file/d/1OQIne-cVGeH6R4nqGGm6Igm3DnsozLhJ/view?usp=drive_link
> > C reproducer: https://drive.google.com/file/d/1iewyTDtNLkXAJSMnREXKNYcUwfN1mAqA/view?usp=drive_link
> > Syzlang reproducer:
> > https://drive.google.com/file/d/17p1lUipZkXyl9xE0_Qanerbg75W6ER5y/view?usp=drive_link
> >
> > If you fix this issue, please add the following tag to the commit:
> > Reported-by: Yikebaer Aizezi <yikebaer61@xxxxxxxxx>
> >
> > WARNING: possible circular locking dependency detected
> > 6.5.0-rc3 #1 Not tainted
> > ------------------------------------------------------
> > syz-executor/13006 is trying to acquire lock:
> > ffff88801ca69130 (sk_lock-AF_CAN){+.+.}-{0:0}, at: lock_sock
> > home/smyl/linux-image/linux-6.5-rc3/./include/net/sock.h:1708 [inline]
> > ffff88801ca69130 (sk_lock-AF_CAN){+.+.}-{0:0}, at:
> > raw_setsockopt+0x3b6/0x1050
> > home/smyl/linux-image/linux-6.5-rc3/net/can/raw.c:607
> >
> > but task is already holding lock:
> > ffffffff8cdca268 (rtnl_mutex){+.+.}-{3:3}, at:
> > raw_setsockopt+0x3ac/0x1050
> > home/smyl/linux-image/linux-6.5-rc3/net/can/raw.c:606
> >
> > which lock already depends on the new lock.
> >
> >
> > the existing dependency chain (in reverse order) is:
> >
> > -> #1 (rtnl_mutex){+.+.}-{3:3}:
> > __mutex_lock_common
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/mutex.c:603
> > [inline]
> > __mutex_lock+0x14f/0x1440
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/mutex.c:747
> > raw_release+0x1bd/0x940
> > home/smyl/linux-image/linux-6.5-rc3/net/can/raw.c:391
> > __sock_release+0xcd/0x290
> > home/smyl/linux-image/linux-6.5-rc3/net/socket.c:654
> > sock_close+0x18/0x20
> > home/smyl/linux-image/linux-6.5-rc3/net/socket.c:1386
> > __fput+0x391/0x9d0
> > home/smyl/linux-image/linux-6.5-rc3/fs/file_table.c:384
> > task_work_run+0x153/0x230
> > home/smyl/linux-image/linux-6.5-rc3/kernel/task_work.c:179
> > resume_user_mode_work
> > home/smyl/linux-image/linux-6.5-rc3/./include/linux/resume_user_mode.h:49
> > [inline]
> > exit_to_user_mode_loop
> > home/smyl/linux-image/linux-6.5-rc3/kernel/entry/common.c:171 [inline]
> > exit_to_user_mode_prepare+0x210/0x240
> > home/smyl/linux-image/linux-6.5-rc3/kernel/entry/common.c:204
> > __syscall_exit_to_user_mode_work
> > home/smyl/linux-image/linux-6.5-rc3/kernel/entry/common.c:286 [inline]
> > syscall_exit_to_user_mode+0x19/0x50
> > home/smyl/linux-image/linux-6.5-rc3/kernel/entry/common.c:297
> > do_syscall_64+0x42/0xb0
> > home/smyl/linux-image/linux-6.5-rc3/arch/x86/entry/common.c:86
> > entry_SYSCALL_64_after_hwframe+0x63/0xcd
> >
> > -> #0 (sk_lock-AF_CAN){+.+.}-{0:0}:
> > check_prev_add
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:3142
> > [inline]
> > check_prevs_add
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:3261
> > [inline]
> > validate_chain
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:3876
> > [inline]
> > __lock_acquire+0x2ecd/0x5b90
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:5144
> > lock_acquire
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:5761
> > [inline]
> > lock_acquire+0x1ad/0x520
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:5726
> > lock_sock_nested+0x34/0xe0
> > home/smyl/linux-image/linux-6.5-rc3/net/core/sock.c:3492
> > lock_sock
> > home/smyl/linux-image/linux-6.5-rc3/./include/net/sock.h:1708 [inline]
> > raw_setsockopt+0x3b6/0x1050
> > home/smyl/linux-image/linux-6.5-rc3/net/can/raw.c:607
> > __sys_setsockopt+0x252/0x510
> > home/smyl/linux-image/linux-6.5-rc3/net/socket.c:2263
> > __do_sys_setsockopt
> > home/smyl/linux-image/linux-6.5-rc3/net/socket.c:2274 [inline]
> > __se_sys_setsockopt
> > home/smyl/linux-image/linux-6.5-rc3/net/socket.c:2271 [inline]
> > __x64_sys_setsockopt+0xb9/0x150
> > home/smyl/linux-image/linux-6.5-rc3/net/socket.c:2271
> > do_syscall_x64
> > home/smyl/linux-image/linux-6.5-rc3/arch/x86/entry/common.c:50
> > [inline]
> > do_syscall_64+0x35/0xb0
> > home/smyl/linux-image/linux-6.5-rc3/arch/x86/entry/common.c:80
> > entry_SYSCALL_64_after_hwframe+0x63/0xcd
> >
> > other info that might help us debug this:
> >
> > Possible unsafe locking scenario:
> >
> > CPU0 CPU1
> > ---- ----
> > lock(rtnl_mutex);
> > lock(sk_lock-AF_CAN);
> > lock(rtnl_mutex);
> > lock(sk_lock-AF_CAN);
> >
> > *** DEADLOCK ***
> >
> > 1 lock held by syz-executor/13006:
> > #0: ffffffff8cdca268 (rtnl_mutex){+.+.}-{3:3}, at:
> > raw_setsockopt+0x3ac/0x1050
> > home/smyl/linux-image/linux-6.5-rc3/net/can/raw.c:606
> >
> > stack backtrace:
> > CPU: 0 PID: 13006 Comm: syz-executor Not tainted 6.5.0-rc3 #1
> > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
> > rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014
> > Call Trace:
> > <TASK>
> > __dump_stack home/smyl/linux-image/linux-6.5-rc3/lib/dump_stack.c:88 [inline]
> > dump_stack_lvl+0x92/0xf0
> > home/smyl/linux-image/linux-6.5-rc3/lib/dump_stack.c:106
> > check_noncircular+0x2ef/0x3d0
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:2195
> > check_prev_add
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:3142
> > [inline]
> > check_prevs_add
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:3261
> > [inline]
> > validate_chain
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:3876
> > [inline]
> > __lock_acquire+0x2ecd/0x5b90
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:5144
> > lock_acquire home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:5761
> > [inline]
> > lock_acquire+0x1ad/0x520
> > home/smyl/linux-image/linux-6.5-rc3/kernel/locking/lockdep.c:5726
> > lock_sock_nested+0x34/0xe0
> > home/smyl/linux-image/linux-6.5-rc3/net/core/sock.c:3492
> > lock_sock home/smyl/linux-image/linux-6.5-rc3/./include/net/sock.h:1708
> > [inline]
> > raw_setsockopt+0x3b6/0x1050
> > home/smyl/linux-image/linux-6.5-rc3/net/can/raw.c:607
> > __sys_setsockopt+0x252/0x510
> > home/smyl/linux-image/linux-6.5-rc3/net/socket.c:2263
> > __do_sys_setsockopt
> > home/smyl/linux-image/linux-6.5-rc3/net/socket.c:2274 [inline]
> > __se_sys_setsockopt
> > home/smyl/linux-image/linux-6.5-rc3/net/socket.c:2271 [inline]
> > __x64_sys_setsockopt+0xb9/0x150
> > home/smyl/linux-image/linux-6.5-rc3/net/socket.c:2271
> > do_syscall_x64
> > home/smyl/linux-image/linux-6.5-rc3/arch/x86/entry/common.c:50
> > [inline]
> > do_syscall_64+0x35/0xb0
> > home/smyl/linux-image/linux-6.5-rc3/arch/x86/entry/common.c:80
> > entry_SYSCALL_64_after_hwframe+0x63/0xcd
> > RIP: 0033:0x47959d
> > Code: 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48
> > 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d
> > 01 f0 ff ff 73 01 c3 48 c7 c1 b4 ff ff ff f7 d8 64 89 01 48
> > RSP: 002b:00007f1c93598068 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
> > RAX: ffffffffffffffda RBX: 000000000059c0a0 RCX: 000000000047959d
> > RDX: 0000000000000002 RSI: 0000000000000065 RDI: 0000000000000003
> > RBP: 000000000059c0a0 R08: 0000000000000004 R09: 0000000000000000
> > R10: 00000000200001c0 R11: 0000000000000246 R12: 000000000059c0ac
> > R13: 000000000000000b R14: 0000000000437250 R15: 00007f1c93578000
> > </TASK>
> >

Next message: Konrad Dybcio: "Re: [PATCH 2/2] ARM: dts: qcom: ipq4019-ap.dk01.1: align flash node with bindings"
Previous message: Robert Marko: "Re: [PATCH 2/2] ARM: dts: qcom: ipq4019-ap.dk01.1: align flash node with bindings"
In reply to: Oliver Hartkopp: "Re: possible deadlock in raw_setsockopt"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]