From: Mike Christie <michaelc@cs.wisc.edu>
To: vikas.chaudhary@qlogic.com
Cc: jbottomley@parallels.com, linux-scsi@vger.kernel.org,
lalit.chandivade@qlogic.com, ravi.anand@qlogic.com
Subject: Re: [PATCH 04/13] qla4xxx: Do not add duplicate CHAP entry in FLASH
Date: Mon, 03 Oct 2011 15:40:39 -0500 [thread overview]
Message-ID: <4E8A1DC7.8040803@cs.wisc.edu> (raw)
In-Reply-To: <1317662967-30110-5-git-send-email-vikas.chaudhary@qlogic.com>
On 10/03/2011 12:29 PM, vikas.chaudhary@qlogic.com wrote:
> From: Lalit Chandivade <lalit.chandivade@qlogic.com>
>
> QLogic applications store the CHAP information in FLASH. During login,
> authentication information is provided using an index into the CHAP region.
>
> In order to support QLogic applications along with iscsiadm, updated the
> LLD to not add duplicate CHAP entries in the CHAP region and preserve the
> existing CHAP info in the CHAP region in FLASH.
> This allows QLogic applications to pre-write the CHAP entries in the CHAP
> region.
>
> With iscsiadm, when the CHAP authentication information is sent to the LLD, the
> LLD searches for the entry in CHAP region in FLASH, if exists then do not add.
> If CHAP entry does not exist then add the CHAP entry in the CHAP region.
>
Does the qlogic app use the bsg flash commands to send down everything
then or how does one app work differently and use the same driver for
everything else?
> +/**
> + * qla4xxx_get_chap_index - Get chap index given user name and secret
> + * @ha: pointer to adapter structure
> + * @username
> + * @secret
You forgot to write some info on those arguments.
next prev parent reply other threads:[~2011-10-03 20:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 17:29 [PATCH 00/13] qla4xxx: Patches for scsi-misc vikas.chaudhary
2011-10-03 17:29 ` [PATCH 01/13] qla4xxx: Add new FLT firmware region vikas.chaudhary
2011-10-03 17:29 ` [PATCH 02/13] qla4xxx: Update license vikas.chaudhary
2011-10-03 17:29 ` [PATCH 03/13] qla4xxx: Fix bidirectional CHAP vikas.chaudhary
2011-10-03 17:29 ` [PATCH 04/13] qla4xxx: Do not add duplicate CHAP entry in FLASH vikas.chaudhary
2011-10-03 20:40 ` Mike Christie [this message]
2011-10-03 20:41 ` Mike Christie
2011-10-04 17:13 ` Vikas Chaudhary
2011-10-03 17:29 ` [PATCH 05/13] qla4xxx: Fix exporting boot targets to sysfs vikas.chaudhary
2011-10-03 20:46 ` Mike Christie
2011-10-03 20:44 ` James Bottomley
2011-10-03 17:29 ` [PATCH 06/13] qla4xxx: Free Device Database (DDB) reserved by FW vikas.chaudhary
2011-10-03 17:29 ` [PATCH 07/13] qla4xxx: Clear DDB map index on the basis of AEN vikas.chaudhary
2011-10-03 17:29 ` [PATCH 08/13] qla4xxx: Fixed session destroy issue on link up-down vikas.chaudhary
2011-10-03 17:29 ` [PATCH 09/13] qla4xxx: Fixed device blocked " vikas.chaudhary
2011-10-03 21:01 ` Mike Christie
2011-10-03 21:16 ` Mike Christie
2011-10-04 17:07 ` Vikas Chaudhary
2011-10-03 17:29 ` [PATCH 10/13] qla4xxx: Fixed active session re-open issue vikas.chaudhary
2011-10-03 17:29 ` [PATCH 11/13] qla4xxx: Fixed target discovery failed issue vikas.chaudhary
2011-10-03 17:29 ` [PATCH 12/13] qla4xxx: updated device id check for BFS vikas.chaudhary
2011-10-03 17:29 ` [PATCH 13/13] qla4xxx: Update driver version to 5.02.00-k8 vikas.chaudhary
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=4E8A1DC7.8040803@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=jbottomley@parallels.com \
--cc=lalit.chandivade@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=ravi.anand@qlogic.com \
--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.