[repost -- apologies if you see this twice]

I tried to apply the patch in your link, but it didn't work. It looks
like some of the pathnames in open-iscsi have changed since this patch
was created.

So I did a little searching to find the new file locations, and,
bottom line, the patch is much more simple now, based on current open-
iscsi sources.

I'm new to this, but I'd like to submit this patch (or something like
it), based on the current sources:

diff --git a/kernel/iscsi_tcp.c b/kernel/iscsi_tcp.c
index daabd46..b81c318 100644
--- a/kernel/iscsi_tcp.c
+++ b/kernel/iscsi_tcp.c
@@ -1976,7 +1976,7 @@ static struct iscsi_transport
iscsi_tcp_transport = {
        .host_template          = &iscsi_sht,
        .conndata_size          = sizeof(struct iscsi_conn),
        .max_conn               = 1,
-       .max_cmd_len            = 16,
+       .max_cmd_len            = SCSI_MAX_VARLEN_CDB_SIZE,
        /* session management */
        .create_session         = iscsi_tcp_session_create,
        .destroy_session        = iscsi_tcp_session_destroy,

I can verify that this patch did work. I tested on a Fedora Core 8
system with a patched 2.6.24-rc7 kernel, and a co-worker tested it on
an unpatched 2.6.26-rc4 under Ubuntu. In both cases, we were able to
send >16-byte CDBs over an iSCSI transport.

Thanks!



On Jun 4, 1:15 am, Boaz Harrosh <[EMAIL PROTECTED]> wrote:
> EddyQ wrote:
> > Does open-iscsi support long CDBs?
>
> You still need one more 
> patch:http://www.spinics.net/lists/linux-scsi/msg26927.html
>
> Mike please push it threw your tree, James has gone mute
>
> Just out of curiosity, what are you using long CDBs for?
>
> Cheers
> Boaz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to