linux-kernel - [BUG] kernel: locking: a possible sleep-in-atomic-context bug in rt_mutex

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <10fdf749-b47c-587c-96cb-9a877d8760ac@gmail.com>
Date:   Thu, 21 Jun 2018 11:14:49 +0800
From:   Jia-Ju Bai <baijiaju1990@...il.com>
To:     peterz@...radead.org, mingo@...hat.com
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [BUG] kernel: locking: a possible sleep-in-atomic-context bug in
 rt_mutex_slowlock()

The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:

[FUNC] schedule
kernel/locking/rtmutex.c, 1223: schedule in rt_mutex_handle_deadlock
kernel/locking/rtmutex.c, 1273: rt_mutex_handle_deadlock in 
rt_mutex_slowlock
kernel/locking/rtmutex.c, 1249: _raw_spin_lock_irqsave in rt_mutex_slowlock

This bug is found by my static analysis tool (DSAC-2) and checked by my
code review.

I do not know how to correctly fix this bug, so I just report them.


Best wishes,
Jia-Ju Bai