From: Douglas Gilbert <dgilbert@interlog.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v4] sg: relax 16 byte cdb restriction
Date: Tue, 17 Dec 2013 16:53:25 -0500 [thread overview]
Message-ID: <52B0C7D5.8060808@interlog.com> (raw)
In-Reply-To: <1387311664.2213.73.camel@dabdike.int.hansenpartnership.com>
On 13-12-17 03:21 PM, James Bottomley wrote:
> On Sun, 2013-12-01 at 17:13 +0100, Douglas Gilbert wrote:
>> ChangeLog:
>> - remove the 16 byte CDB (SCSI command) length limit
>> from the sg driver by handling longer CDBs the same
>> way as the bsg driver. Remove comment from sg.h
>> public interface about the cmd_len field being
>> limited to 16 bytes.
>> - remove some dead code caused by this change
>> - cleanup comment block at the top of sg.h, fix urls
>>
>> Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>
>
> This doesn't apply:
>
> patching file drivers/scsi/sg.c
> Hunk #1 succeeded at 74 (offset 1 line).
> Hunk #2 succeeded at 164 (offset 2 lines).
> Hunk #3 succeeded at 569 (offset -5 lines).
> Hunk #4 FAILED at 606.
> Hunk #5 succeeded at 678 (offset -6 lines).
> Hunk #6 FAILED at 1660.
> Hunk #7 succeeded at 1742 (offset -11 lines).
> 2 out of 7 hunks FAILED -- saving rejects to file drivers/scsi/sg.c.rej
>
> It looks like there's a missing intermediate patch changing the way
> logging is done within the driver ... I don't recall seeing such a patch
> on the list.
It based on this patch:
http://www.spinics.net/lists/linux-scsi/msg69957.html
sent to the list on 12 November titled:
[PATCH v3] sg: O_EXCL and other lock handling
and it was followed in the same day by:
[PATCH v3] sg: relax 16 byte cdb restriction
which you commented on, hence "v4" that started this thread.
The vagueness in the "O_EXCL" post about the reported failure
in the vicinity of sg_remove() was cleared up a few days later
by this post:
http://www.spinics.net/lists/linux-scsi/msg70006.html
You might check if the fix to the st driver for this matter has
made it into your tree or further.
I'm told the "O_EXCL" patch has been tested by a major vendor
with help from another frequent correspondent to this list.
Doug Gilbert
prev parent reply other threads:[~2013-12-17 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 16:13 [PATCH v4] sg: relax 16 byte cdb restriction Douglas Gilbert
2013-12-17 20:21 ` James Bottomley
2013-12-17 21:53 ` Douglas Gilbert [this message]
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=52B0C7D5.8060808@interlog.com \
--to=dgilbert@interlog.com \
--cc=James.Bottomley@HansenPartnership.com \
--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).