diff options
author | 2024-08-20 11:31:48 +0800 | |
---|---|---|
committer | 2024-08-20 16:27:22 +0200 | |
commit | 6cb9df81a2c462b89d2f9611009ab43ae8717841 (patch) | |
tree | 0f039fa50d155416b092e9cf0774015891122b64 /scripts/lib/kdoc/kdoc_parser.py | |
parent | gfs2: Minor gfs2_glock_cb cleanup (diff) | |
download | wireguard-linux-6cb9df81a2c462b89d2f9611009ab43ae8717841.tar.xz wireguard-linux-6cb9df81a2c462b89d2f9611009ab43ae8717841.zip |
gfs2: fix double destroy_workqueue error
When gfs2_fill_super() fails, destroy_workqueue() is called within
gfs2_gl_hash_clear(), and the subsequent code path calls
destroy_workqueue() on the same work queue again.
This issue can be fixed by setting the work queue pointer to NULL after
the first destroy_workqueue() call and checking for a NULL pointer
before attempting to destroy the work queue again.
Reported-by: syzbot+d34c2a269ed512c531b0@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=d34c2a269ed512c531b0
Fixes: 30e388d57367 ("gfs2: Switch to a per-filesystem glock workqueue")
Cc: stable@vger.kernel.org
Signed-off-by: Julian Sun <sunjunchao2870@gmail.com>
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_parser.py')
0 files changed, 0 insertions, 0 deletions