[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210702091831.615042-1-desmondcheongzx@gmail.com>
Date: Fri, 2 Jul 2021 17:18:29 +0800
From: Desmond Cheong Zhi Xi <desmondcheongzx@...il.com>
To: jlayton@...nel.org, bfields@...ldses.org, viro@...iv.linux.org.uk
Cc: Desmond Cheong Zhi Xi <desmondcheongzx@...il.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
skhan@...uxfoundation.org, gregkh@...uxfoundation.org,
linux-kernel-mentees@...ts.linuxfoundation.org
Subject: [PATCH 0/2] fcntl: fix potential deadlocks
Hi,
Syzbot reports a possible irq lock inversion dependency:
https://syzkaller.appspot.com/bug?id=923cfc6c6348963f99886a0176ef11dcc429547b
While investigating this error, I discovered that multiple similar lock inversion scenarios can occur. Hence, this series addresses potential deadlocks for two classes of locks, one in each patch:
1. Fix potential deadlocks for &fown_struct.lock
2. Fix potential deadlock for &fasync_struct.fa_lock
Best wishes,
Desmond
Desmond Cheong Zhi Xi (2):
fcntl: fix potential deadlocks for &fown_struct.lock
fcntl: fix potential deadlock for &fasync_struct.fa_lock
fs/fcntl.c | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
--
2.25.1
Powered by blists - more mailing lists