linux-kernel - [BUG] scsi/fcoe: Sleep-in-atomic bugs in fcoe driver

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: <a19f782f-b3f2-c954-f982-35574b36d605@163.com>
Date:   Tue, 3 Oct 2017 11:02:33 +0800
From:   Jia-Ju Bai <baijiaju1990@....com>
To:     jth@...nel.org, jejb@...ux.vnet.ibm.com, martin.petersen@...cle.com
Cc:     fcoe-devel@...n-fcoe.org, linux-scsi@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: [BUG] scsi/fcoe: Sleep-in-atomic bugs in fcoe driver

According to fcoe_ctlr.c, the driver may sleep under a RCU lock,
and the function call paths are:
fcoe_ctlr_disc_stop_locked (acquire the RCU lock)
   fc_rport_logoff
     mutex_lock --> may sleep

fcoe_ctlr_vn_disc
   fc_rport_login
     mutex_lock --> may sleep

fcoe_ctlr_vn_age
   fc_rport_logoff
     mutex_lock --> may sleep

These bugs are found by my static analysis tool and my code review.

Thanks,
Jia-Ju Bai