All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: kkv@clodo.ru, linux-scsi@vger.kernel.org
Subject: Re: threads scsi_eh_ and scsi_tmf_ don't die when ib_srp reconnect
Date: Mon, 10 Aug 2015 08:30:35 -0700	[thread overview]
Message-ID: <55C8C39B.1010000@sandisk.com> (raw)
In-Reply-To: <55C8C0DC.7070505@clodo.ru>

On 08/10/2015 08:18 AM, Konstantin Krotov wrote:
> I was faced with the following problem:
>
> Im exported to compute-node scsi disks through ib_srp from storages. And
> if reconnect occurs for any reason, eg
>
> "[1201117.626498] scsi host62: ib_srp: REJ received
> [1201117.626507] scsi host62: ib_srp: SRP LOGIN from
> fe80:0000:0000:0000:0002:c903:0009:1796 to
> fe80:0000:0000:0000:0002:c903:0009:c1a0 REJECTED, reason 0x00010001
> [1201117.626656] scsi host62: ib_srp: Connection 0/8 failed"
>
> i find threads in output ps:
> "root     28047  0.0  0.0      0     0 ?        S    18:04   0:00
> [scsi_eh_62]
> root     28048  0.0  0.0      0     0 ?        S<   18:04   0:00
> [scsi_tmf_62]"
>
> Each reconnect generates two thread, which do not die.
>
> kernel version 3.19.1
>
> modinfo ib_srp
> filename:       /lib/modules/3.19-3-amd64/updates/dkms/ib_srp.ko
> release_date:   Apr 09 2015
> version:        2.0.32#in-tree

Hello Konstantin,

Does the above output mean that you are using the ib_srp-backport driver 
? If so, please upgrade to version v2.0.34. That version includes all 
SRP initiator fixes that have been posted on the linux-rdma and 
linux-scsi mailing lists for inclusion in Linux kernel v4.3.

Bart.


  reply	other threads:[~2015-08-10 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 15:18 threads scsi_eh_ and scsi_tmf_ don't die when ib_srp reconnect Konstantin Krotov
2015-08-10 15:30 ` Bart Van Assche [this message]
2015-08-11 13:40   ` Konstantin Krotov
2015-08-11 20:28     ` Bart Van Assche
2015-08-12  5:15       ` Konstantin Krotov
2015-08-12 16:50         ` Bart Van Assche
2015-08-14  9:06           ` Konstantin Krotov
2015-08-14 16:10             ` 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=55C8C39B.1010000@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=kkv@clodo.ru \
    --cc=linux-scsi@vger.kernel.org \
    /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.