linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 111441] iscsi fails to attach to targets
Date: Mon, 22 Feb 2016 11:36:09 +0000	[thread overview]
Message-ID: <bug-111441-11613-IdSGohvHVe@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-111441-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=111441

--- Comment #18 from Serguei Bezverkhi <sbezverk@cisco.com> ---
Hello Hannes,

Thank you for your reply. I am on 4.4.2 kernel, is there any chance to commit
it in 4.4 as well? If not, could you send me diff for 4.4 kernel.

Best regards

Serguei


Serguei Bezverkhi,
TECHNICAL LEADER.SERVICES
Global SP Services
sbezverk@cisco.com
Phone: +1 416 306 7312
Mobile: +1 514 234 7374

CCIE (R&S,SP,Sec) - #9527

Cisco.com



 Think before you print.
This email may contain confidential and privileged material for the sole use of
the intended recipient. Any review, use, distribution or disclosure by others
is strictly prohibited. If you are not the intended recipient (or authorized to
receive for the recipient), please contact the sender by reply email and delete
all copies of this message.
Please click here for Company Registration Information.




-----Original Message-----
From: Hannes Reinecke [mailto:hare@suse.de] 
Sent: Monday, February 22, 2016 2:08 AM
To: Serguei Bezverkhi (sbezverk) <sbezverk@cisco.com>; Mike Christie
<michaelc@cs.wisc.edu>
Cc: bugzilla-daemon@bugzilla.kernel.org; linux-scsi@vger.kernel.org; Christoph
Hellwig <hch@infradead.org>
Subject: Re: [Bug 111441] New: iscsi fails to attach to targets

On 02/22/2016 01:45 AM, Serguei Bezverkhi (sbezverk) wrote:
> Hi Mike,
> 
> I just wanted to follow up with you to see if the patch got committed to an upstream kernel if yes, please let me into which version it went.
> 
> Thank you
> 
> Serguei
> 
> 
> Serguei Bezverkhi,
> TECHNICAL LEADER.SERVICES
> Global SP Services
> sbezverk@cisco.com
> Phone: +1 416 306 7312
> Mobile: +1 514 234 7374
> 
> CCIE (R&S,SP,Sec) - #9527
> 
> Cisco.com
> 
> 
> 
>  Think before you print.
> This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
> Please click here for Company Registration Information.
> 
> 
> 
> -----Original Message-----
> From: Mike Christie [mailto:michaelc@cs.wisc.edu]
> Sent: Friday, January 29, 2016 6:33 PM
> To: Serguei Bezverkhi (sbezverk) <sbezverk@cisco.com>
> Cc: bugzilla-daemon@bugzilla.kernel.org; linux-scsi@vger.kernel.org; 
> Christoph Hellwig <hch@infradead.org>; Hannes Reinecke <hare@suse.de>
> Subject: Re: [Bug 111441] New: iscsi fails to attach to targets
> 
> On 01/29/2016 04:21 PM, Serguei Bezverkhi (sbezverk) wrote:
>> HI Mike,
>>
>> I tried your patch and it is has eliminated first traceback but I still do not see my remote targets.
>>
> 
> That is sort of expected. Your target is not setup for ALUA properly. It says it supports ALUA, but when scsi_dh_alua asks about the ports it is reporting there are none. Ccing the people that made the patch that added the issue and own the code.
> 
> Hey Christoph and Hannes,
> 
> The dh/alua changes that added this:
> 
>         error = scsi_dh_add_device(sdev);
>         if (error) {
>                 sdev_printk(KERN_INFO, sdev,
>                                 "failed to add device handler: %d\n", error);
>                 return error;
>         }
> 
> to scsi_sysfs_add_sdev are adding a regression.
> 
> 1. If that fails, then we forget to do device_del before doing the return. My patch in this thread added that back, so we do not see the sysfs oopses anymore. But.....
> 
> 2. It looks like in older kernels, we would allow misconfigured targets like this one to still setup devices. Do we want that old behavior back?
> Should we just ignore the return value from scsi_dh_add_device above?
> Note that in this case, it is LIO so it can be easily fixed on the target side by just setting it up properly. I do not think other targets would hit this type of issue.
> 
> 
This has been fixed up with my patchset to update the ALUA handler, most
notably the commit 'scsi: ignore errors from scsi_dh_add_device()' which was
included in 4.5.

Cheers,

Hannes

-- 
You are receiving this mail because:
You are the assignee for the bug.--
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

  parent reply	other threads:[~2016-02-22 11:36 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 22:51 [Bug 111441] New: iscsi fails to attach to targets bugzilla-daemon
2016-01-29  1:53 ` Mike Christie
2016-01-29  2:13   ` Mike Christie
2016-01-29  2:55   ` Serguei Bezverkhi (sbezverk)
2016-01-29  8:01     ` Michael Christie
2016-01-29  8:25       ` Mike Christie
2016-01-29 12:04       ` Serguei Bezverkhi (sbezverk)
2016-01-29 19:08         ` Michael Christie
2016-01-29 19:11           ` Serguei Bezverkhi (sbezverk)
2016-01-29 19:26             ` Mike Christie
2016-01-29 22:21               ` Serguei Bezverkhi (sbezverk)
2016-01-29 23:32                 ` Mike Christie
2016-01-30  7:38                   ` Nicholas A. Bellinger
2016-02-01 16:55                     ` Mike Christie
2016-02-02 16:41                       ` Serguei Bezverkhi (sbezverk)
2016-02-02 22:56                       ` Nicholas A. Bellinger
2016-02-02 23:21                         ` Serguei Bezverkhi (sbezverk)
2016-02-08  8:01                         ` Nicholas A. Bellinger
2016-02-16 19:08                           ` Hannes Reinecke
2016-02-27 22:15                             ` Nicholas A. Bellinger
2016-02-02 18:09                   ` Christoph Hellwig
2016-02-02 20:12                     ` Mike Christie
2016-02-02 20:25                       ` Serguei Bezverkhi (sbezverk)
2016-02-02 21:54                       ` Serguei Bezverkhi (sbezverk)
2016-02-22  0:45                   ` Serguei Bezverkhi (sbezverk)
2016-02-22  7:08                     ` Hannes Reinecke
2016-02-22 11:36                       ` Serguei Bezverkhi (sbezverk)
2016-01-29  3:00 ` [Bug 111441] " bugzilla-daemon
2016-01-29  3:05 ` bugzilla-daemon
2016-01-29  3:32 ` bugzilla-daemon
2016-01-29  3:40 ` bugzilla-daemon
2016-01-29 12:04 ` bugzilla-daemon
2016-01-29 19:11 ` bugzilla-daemon
2016-01-29 22:21 ` bugzilla-daemon
2016-01-30  7:46 ` bugzilla-daemon
2016-02-01  2:13 ` bugzilla-daemon
2016-02-02 16:41 ` bugzilla-daemon
2016-02-02 20:25 ` bugzilla-daemon
2016-02-02 22:03 ` bugzilla-daemon
2016-02-02 22:56 ` bugzilla-daemon
2016-02-02 23:21 ` bugzilla-daemon
2016-02-08  8:01 ` bugzilla-daemon
2016-02-22  0:45 ` bugzilla-daemon
2016-02-22  7:08 ` bugzilla-daemon
2016-02-22 11:36 ` bugzilla-daemon [this message]
2016-02-27 22:15 ` bugzilla-daemon

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=bug-111441-11613-IdSGohvHVe@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).