From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Hannes Reinecke <hare@suse.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Ewan Milne <emilne@redhat.com>,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCHv6 00/23] ALUA device handler update, part II
Date: Fri, 12 Feb 2016 11:28:23 -0800 [thread overview]
Message-ID: <56BE3257.9070808@sandisk.com> (raw)
In-Reply-To: <1455265546-44470-1-git-send-email-hare@suse.de>
On 02/12/2016 12:25 AM, Hannes Reinecke wrote:
> as promised here is now the second part of my ALUA device handler update.
Hello Hannes,
Thanks for the quick respin. The first lockdep warning I noticed with the
previous version is gone. But I saw the following with this patch series:
------------[ cut here ]------------
WARNING: CPU: 7 PID: 43 at kernel/locking/mutex.c:869 mutex_trylock+0x1ad/0x1c0()
DEBUG_LOCKS_WARN_ON(in_interrupt())
CPU: 7 PID: 43 Comm: ksoftirqd/7 Tainted: G E 4.5.0-rc3+ #8
Call Trace:
[<ffffffff81263ba7>] dump_stack+0x6b/0xa4
[<ffffffff81057acb>] warn_slowpath_common+0x8b/0xd0
[<ffffffff81057bb1>] warn_slowpath_fmt+0x41/0x70
[<ffffffff815307bd>] mutex_trylock+0x1ad/0x1c0
[<ffffffffa041c731>] alua_check+0x31/0x260 [scsi_dh_alua]
[<ffffffffa041c9ce>] alua_check_sense+0x6e/0x90 [scsi_dh_alua]
[<ffffffff8136adf1>] scsi_check_sense+0x71/0x270
[<ffffffff8136b1ee>] scsi_decide_disposition+0x18e/0x200
[<ffffffff81371065>] scsi_softirq_done+0x65/0x150
[<ffffffff812495d1>] __blk_mq_complete_request+0x81/0x100
[<ffffffff812496e7>] blk_mq_complete_request+0x17/0x20
[<ffffffff8136f4d6>] scsi_mq_done+0x16/0x20
[<ffffffffa03f112e>] srp_process_rsp+0x13e/0x280 [ib_srp]
[<ffffffffa03f4127>] srp_recv_done+0x187/0x380 [ib_srp]
[<ffffffffa012f3f3>] __ib_process_cq+0x43/0xc0 [ib_core]
[<ffffffffa012f7cd>] ib_poll_handler+0x2d/0x80 [ib_core]
[<ffffffff81294c88>] irq_poll_softirq+0xa8/0xf0
[<ffffffff8105be66>] __do_softirq+0xf6/0x240
[<ffffffff8105bfca>] run_ksoftirqd+0x1a/0x60
[<ffffffff8107cf43>] smpboot_thread_fn+0x113/0x1d0
[<ffffffff810793e4>] kthread+0xe4/0x100
[<ffffffff81534eff>] ret_from_fork+0x3f/0x70
---[ end trace 34fb3b7c104f6c3d ]---
Can you also address this warning ?
Thanks,
Bart.
prev parent reply other threads:[~2016-02-12 19:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 8:25 [PATCHv6 00/23] ALUA device handler update, part II Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 01/23] scsi_dh_alua: Pass buffer as function argument Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 02/23] scsi_dh_alua: separate out alua_stpg() Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 03/23] scsi_dh_alua: Make stpg synchronous Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 04/23] scsi_dh_alua: call alua_rtpg() if stpg fails Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 05/23] scsi_dh_alua: switch to scsi_execute_req_flags() Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 06/23] scsi_dh_alua: allocate RTPG buffer separately Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 07/23] scsi_dh_alua: Use separate alua_port_group structure Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 08/23] scsi_dh_alua: use unique device id Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 09/23] scsi_dh_alua: simplify alua_initialize() Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 10/23] revert commit a8e5a2d593cb ("[SCSI] scsi_dh_alua: ALUA handler attach should succeed while TPG is transitioning") Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 11/23] scsi_dh_alua: move optimize_stpg evaluation Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 12/23] scsi_dh_alua: remove 'rel_port' from alua_dh_data structure Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 13/23] scsi_dh_alua: Use workqueue for RTPG Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 14/23] scsi_dh_alua: Allow workqueue to run synchronously Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 15/23] scsi_dh_alua: Add new blacklist flag 'BLIST_SYNC_ALUA' Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 16/23] scsi_dh_alua: Recheck state on unit attention Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 17/23] scsi_dh_alua: update all port states Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 18/23] scsi_dh_alua: Send TEST UNIT READY to poll for transitioning Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 19/23] scsi_dh: add 'rescan' callback Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 20/23] scsi: Add 'access_state' attribute Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 21/23] scsi_dh_alua: use common definitions for ALUA state Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 22/23] scsi_dh_alua: update 'access_state' field Hannes Reinecke
2016-02-12 8:25 ` [PATCHv6 23/23] scsi_dh_alua: Update version to 2.0 Hannes Reinecke
2016-02-12 19:28 ` Bart Van Assche [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=56BE3257.9070808@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=emilne@redhat.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=jthumshirn@suse.de \
--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.