From: Mike Christie <michaelc@cs.wisc.edu>
To: markh@compro.net
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: New 2.6.24.2 SG_IO SCSI problems
Date: Fri, 22 Feb 2008 10:59:11 -0600 [thread overview]
Message-ID: <47BEFF5F.9020002@cs.wisc.edu> (raw)
In-Reply-To: <47BEFD4B.9060803@cs.wisc.edu>
Mike Christie wrote:
> Mark Hounschell wrote:
>> I seem to have run into some sort of regression in the SG_IO interface
>> of 2.6.24.2. I have an application that up until 2.6.24 worked fine.
>> The 2.6.23.16 kernel works fine.
>>
>> During reads I get these kernel messages. Writes and other functions
>> _seem_ OK. Actually basic
>> reads are working. Its with large BC reads using an io_vec list that
>> the problem shows up.
>>
>
> Are you doing SG_IO to the sg device (/dev/sg*) or to the block device
> (/dev/sdX)?
If you are doing SG_IO to the sg device, then I know of one regression
(well not regression exactly, but I fixed a bug but the patch got
partially overwritten by another patch and that caused a new bug). Both
bugs are fixed in 2.6.25-rc2. Could you try that out if you are doing
SG_IO to the sg device.
next prev parent reply other threads:[~2008-02-22 16:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 15:15 New 2.6.24.2 SG_IO SCSI problems Mark Hounschell
2008-02-21 15:41 ` James Bottomley
2008-02-21 16:21 ` Mark Hounschell
2008-02-22 10:03 ` Mark Hounschell
2008-02-22 16:50 ` Mike Christie
2008-02-22 16:59 ` Mike Christie [this message]
2008-02-22 17:56 ` Mark Hounschell
2008-02-22 21:38 ` Mark Hounschell
2008-02-22 22:25 ` Mike Christie
2008-02-22 22:48 ` Tony Battersby
2008-02-23 11:16 ` Mark Hounschell
2008-03-05 11:58 ` Mark Hounschell
2008-03-05 15:44 ` James Bottomley
2008-03-05 16:28 ` Mark Hounschell
2008-03-05 17:13 ` Mike 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=47BEFF5F.9020002@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=markh@compro.net \
/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