From: Mike Christie <michaelc@cs.wisc.edu>
To: "Serguei Bezverkhi (sbezverk)" <sbezverk@cisco.com>
Cc: "bugzilla-daemon@bugzilla.kernel.org"
<bugzilla-daemon@bugzilla.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [Bug 111441] New: iscsi fails to attach to targets
Date: Fri, 29 Jan 2016 13:26:55 -0600 [thread overview]
Message-ID: <56ABBCFF.9060003@cs.wisc.edu> (raw)
In-Reply-To: <4c4653b259cd4f1887505dfc61d500a8@XCH-ALN-006.cisco.com>
[-- Attachment #1: Type: text/plain, Size: 2413 bytes --]
On 01/29/2016 01:11 PM, Serguei Bezverkhi (sbezverk) wrote:
> If you send me the diff for your patch, I will build new kernel myself.
>
Bugzilla must be messing something up. I attached to one of the previous
mails. Attaching it here again.
Email me offlist and without bugzilla if you do not get it here.
The patch will fix the syfs bug ons you are hitting.
I am not sure if it will fix the genhd one. We can deal with that one
next if it is a different issue.
> 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: Michael Christie [mailto:michaelc@cs.wisc.edu]
> Sent: Friday, January 29, 2016 2:09 PM
> To: Serguei Bezverkhi (sbezverk) <sbezverk@cisco.com>
> Cc: bugzilla-daemon@bugzilla.kernel.org; linux-scsi@vger.kernel.org
> Subject: Re: [Bug 111441] New: iscsi fails to attach to targets
>
>
>> On Jan 29, 2016, at 6:04 AM, Serguei Bezverkhi (sbezverk) <sbezverk@cisco.com> wrote:
>>
>> Actually this server uses both cases: Local taregts (since it is OpenStack server) and remote targets as it tries to mount 4 remotefile systems.
>>
>> You are correct, I always use the same box I just change the kernel it is using to boot. No other changes to the environment. I do not mind to load a test kernel without that suspected patch, just get me the RPM.
>>
>
> I do not know what you mean. I think the patch I sent will fix the sysfs errors caused due to alua not being setup properly on your system and scsi_dh_alua failing to attach. That patch should be applied to the 4.4 upstream kernel. Are you saying you want me to make you a kernel rpm?
> --
> 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
>
[-- Attachment #2: fix-add-dev-alua-attach-fail-regression.patch --]
[-- Type: text/x-patch, Size: 389 bytes --]
diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
index 21930c9..4269cbc 100644
--- a/drivers/scsi/scsi_sysfs.c
+++ b/drivers/scsi/scsi_sysfs.c
@@ -1061,6 +1061,7 @@ int scsi_sysfs_add_sdev(struct scsi_device *sdev)
if (error) {
sdev_printk(KERN_INFO, sdev,
"failed to add device handler: %d\n", error);
+ device_del(&sdev->sdev_gendev);
return error;
}
next prev parent reply other threads:[~2016-01-29 19:27 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 [this message]
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
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=56ABBCFF.9060003@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sbezverk@cisco.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;
as well as URLs for NNTP newsgroup(s).