From: Hannes Reinecke <hare@suse.de>
To: Bart Van Assche <bart.vanassche@sandisk.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, Ewan Milne <emilne@redhat.com>,
James Bottomley <james.bottomley@hansenpartnership.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] libfc: replace 'rp_mutex' with 'rp_lock'
Date: Tue, 17 May 2016 08:46:25 +0200 [thread overview]
Message-ID: <573ABE41.5000402@suse.de> (raw)
In-Reply-To: <5733455B.7050903@sandisk.com>
On 05/11/2016 04:44 PM, Bart Van Assche wrote:
> On 05/10/16 23:07, Hannes Reinecke wrote:
>> On 05/11/2016 07:49 AM, Hannes Reinecke wrote:
>> RIP: 0010:[<ffffffffa00b2adb>] [<ffffffffa00b2adb>]
>> fc_rport_lookup+0x4b/0x70 [libfc]
>> Call Trace:
>> [<ffffffffa00b2e17>] fc_rport_create+0x17/0x1b0 [libfc]
>> [<ffffffffa00a9f81>] fc_disc_recv_req+0x261/0x480 [libfc]
>> [<ffffffffa00b1008>] fc_lport_recv_els_req+0x68/0x130 [libfc]
>> [<ffffffffa00afd5a>] fc_lport_recv_req+0x9a/0xf0 [libfc]
>> [<ffffffffa00e8333>] fnic_handle_frame+0x63/0xd0 [fnic]
>> [<ffffffff8106fd52>] process_one_work+0x172/0x420
>> [<ffffffff810709ca>] worker_thread+0x11a/0x3c0
>> [<ffffffff81077344>] kthread+0xb4/0xc0
>> [<ffffffff81521318>] ret_from_fork+0x58/0x90
>
> Hello Hannes,
>
> Thanks for sharing this information. fc_disc_recv_req() protects the
> fc_rport_create() call via a mutex (disc_mutex). Since a mutex_lock()
> call may sleep it can trigger the start of an RCU grace period. I think
> this may result in freeing of an rport while fc_rport_lookup() is
> examining it. Have you already considered to add a
> rcu_read_lock()/rcu_read_unlock() pair in fc_rport_lookup()?
>
No, I haven't so far.
This issue is hard to trigger, and I've only got the customer report to
go by.
Also, when using an rcu_read_lock() here one probably needs to revisit
the entire locking structure in libfc:
rport list is an RCU-proctected list, so in principle one only needs to
hold the rport mutex when _assigning_ new rports, and _could_ drop the
mutex usage for a simple lookup.
But this really needs some more thought and testing, so I haven't
attempted it.
Also, with your suggestion I would need to take the mutex_lock _and_
call rcu_read_lock(), which just looks wrong.
Hence I prefer to use the spin_lock method (which, incidentally, is also
suggested in the RCU documentation).
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-05-17 6:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 8:01 [PATCH] libfc: replace 'rp_mutex' with 'rp_lock' Hannes Reinecke
2016-04-25 20:26 ` Ewan D. Milne
2016-05-09 12:29 ` Johannes Thumshirn
2016-05-10 18:33 ` Bart Van Assche
2016-05-11 1:48 ` Martin K. Petersen
2016-05-11 5:49 ` Hannes Reinecke
2016-05-11 6:07 ` Hannes Reinecke
2016-05-11 14:44 ` Bart Van Assche
2016-05-17 6:46 ` Hannes Reinecke [this message]
2016-05-17 18:04 ` Bart Van Assche
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=573ABE41.5000402@suse.de \
--to=hare@suse.de \
--cc=bart.vanassche@sandisk.com \
--cc=emilne@redhat.com \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.