linux-kernel - [BUG] mm/vmalloc: ___might_sleep is called under a spinlock in __purge_vmap_area

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]

Date:   Mon, 9 Oct 2017 12:00:33 +0800
From:   Jia-Ju Bai <baijiaju1990@....com>
To:     akpm@...ux-foundation.org, mhocko@...e.com, mingo@...nel.org,
        catalin.marinas@....com, labbott@...hat.com, thgarnie@...gle.com,
        kirill.shutemov@...ux.intel.com, aryabinin@...tuozzo.com,
        ard.biesheuvel@...aro.org, zijun_hu@....com
Cc:     linux-mm@...ck.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [BUG] mm/vmalloc: ___might_sleep is called under a spinlock in
 __purge_vmap_area_lazy

The ___might_sleep is called under a spinlock, and the function call 
graph is:
__purge_vmap_area_lazy (acquire the spinlock)
   cond_resched_lock
     ___might_sleep

In this situation, ___might_sleep may prints error log message because a 
spinlock is held.
A possible fix is to remove ___might_sleep in cond_resched_lock.

This bug is found by my static analysis tool and my code review.


Thanks,
Jia-Ju Bai