From: Mike Christie <michaelc@cs.wisc.edu>
To: Minh Duc Tran <MinhDuc.Tran@Emulex.Com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: Jayamohan Kallickal <Jayamohan.Kallickal@Emulex.Com>,
Vikas Chaudhary <vikas.chaudhary@qlogic.com>
Subject: Re: [PATCH 1/1] be2iscsi: add block valid bit to iBFT flag
Date: Mon, 10 Nov 2014 11:37:06 -0600 [thread overview]
Message-ID: <5460F7C2.6040205@cs.wisc.edu> (raw)
In-Reply-To: <84b5cd32-3bb6-4541-bbc1-4cbe92c074c6@CMEXHTCAS2.ad.emulex.com>
Adding Vikas to verify if qla4xxx has the same issue.
On 11/10/2014 12:52 AM, Minh Duc Tran wrote:
> From: Minh Tran minhduc.tran@emulex.com <mailto:minhduc.tran@emulex.com>
>
>
>
> We are starting to see problems with certain open-iscsi
> versions out there checking block valid bit. Iscsi boot target login
> will not happen without this bit being set.
>
What versions of open-iscsi? Is it just the SUSE based versions?
>
>
> Signed-off-by: Minh Tran <minhduc.tran@emulex.com>
>
> ---
>
> scsi/be2iscsi/be_main.c | 4 ++--
>
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
>
>
> diff --git a/scsi/be2iscsi/be_main.c b/scsi/be2iscsi/be_main.c
>
> index 30d74a0..aacf223 100644
>
> --- a/scsi/be2iscsi/be_main.c
>
> +++ b/scsi/be2iscsi/be_main.c
>
> @@ -429,7 +429,7 @@ static ssize_t beiscsi_show_boot_tgt_info(void
> *data, int type, char *buf)
>
> auth_data.chap.intr_secret);
>
> break;
>
> case ISCSI_BOOT_TGT_FLAGS:
>
> - rc = sprintf(str, "2\n");
>
> + rc = sprintf(str, "3\n");
>
> break;
>
> case ISCSI_BOOT_TGT_NIC_ASSOC:
>
> rc = sprintf(str, "0\n");
>
> @@ -466,7 +466,7 @@ static ssize_t beiscsi_show_boot_eth_info(void
> *data, int type, char *buf)
>
>
>
> switch (type) {
>
> case ISCSI_BOOT_ETH_FLAGS:
>
> - rc = sprintf(str, "2\n");
>
> + rc = sprintf(str, "3\n");
>
> break;
>
> case ISCSI_BOOT_ETH_INDEX:
>
> rc = sprintf(str, "0\n");
>
I think we want to move SYSFS_FLAG_FW_SEL_BOOT from ql4_def.h to
include/linux/iscsi_boot_sysfs.h (also add a ISCSI_BOOT_ prefix), and
then have both drivers use it.
next parent reply other threads:[~2014-11-10 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <84b5cd32-3bb6-4541-bbc1-4cbe92c074c6@CMEXHTCAS2.ad.emulex.com>
2014-11-10 17:37 ` Mike Christie [this message]
2014-11-10 18:07 ` [PATCH 1/1] be2iscsi: add block valid bit to iBFT flag Minh Duc Tran
2014-11-11 11:36 ` Vikas Chaudhary
2015-01-12 23:05 Minh Duc Tran
2015-01-15 23:16 ` Mike Christie
2015-01-15 23:26 ` James Bottomley
2015-01-16 1:26 ` Minh Duc Tran
2015-01-16 16:27 ` Michael Christie
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=5460F7C2.6040205@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=Jayamohan.Kallickal@Emulex.Com \
--cc=MinhDuc.Tran@Emulex.Com \
--cc=linux-scsi@vger.kernel.org \
--cc=vikas.chaudhary@qlogic.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.