From: Johannes Thumshirn <jthumshirn@suse.de>
To: Jia-Ju Bai <baijiaju1990@163.com>
Cc: jth@kernel.org, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, fcoe-devel@open-fcoe.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] scsi/fcoe: Sleep-in-atomic bugs in fcoe driver
Date: Wed, 4 Oct 2017 12:06:37 +0200 [thread overview]
Message-ID: <20171004100637.pucskthcimhhen4k@linux-x5ow.site> (raw)
In-Reply-To: <a19f782f-b3f2-c954-f982-35574b36d605@163.com>
On Tue, Oct 03, 2017 at 11:02:33AM +0800, Jia-Ju Bai wrote:
> 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
>
Thanks for the report, coincidentally I have a bug report for this as well (in
a real setup not just static analysis) and gave the reporter a patch to test.
Once it's verified I'll post it here.
Thanks,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
prev parent reply other threads:[~2017-10-04 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 3:02 [BUG] scsi/fcoe: Sleep-in-atomic bugs in fcoe driver Jia-Ju Bai
2017-10-04 10:06 ` Johannes Thumshirn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171004100637.pucskthcimhhen4k@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=baijiaju1990@163.com \
--cc=fcoe-devel@open-fcoe.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=jth@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox