On Wed, Feb 24, 2016 at 04:22:28PM -0800, Derek Basehore wrote:
> This allows scsi devices to remain runtime suspended for system
> suspend. Since runtime suspend is stricter than system suspend
> callbacks, this is just returning a positive number for the prepare
> callback.
AFAICT SCSI layer alr
Apply for a loan at 3% reply to this Email for more Info
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Feb 12, 2016 at 12:30 AM, Himanshu Madhani
wrote:
> Hi Nic,
>
>
>
> On 2/11/16, 3:47 PM, "Nicholas A. Bellinger" wrote:
>
>>On Wed, 2016-02-10 at 22:53 -0800, Nicholas A. Bellinger wrote:
>>> On Tue, 2016-02-09 at 18:03 +, Himanshu Madhani wrote:
>>> > On 2/8/16, 9:25 PM, "Nicholas A.
On 27 February 2016 at 06:12, Martin K. Petersen
wrote:
>
> "A MAXIMUM WRITE SAME LENGTH field set to zero indicates that the device
> server does not report a limit on the number of logical blocks that it
> allows to be unmapped or written in a single WRITE SAME command."
>
> I.e. that parameter
https://bugzilla.kernel.org/show_bug.cgi?id=106841
--- Comment #2 from Tom Yan ---
This commit did NOT fix anything:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=3417c1b5cb1fdc10261dbed42b05cc93166a78fd
Only the error changes from:
scsi 7:0:0:1: F
https://bugzilla.kernel.org/show_bug.cgi?id=106841
Tom Yan changed:
What|Removed |Added
Kernel Version|4.2.4 |4.4.1
--
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=106841
Tom Yan changed:
What|Removed |Added
Summary|do not output error for |ses: do not output error
|si
tree:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgit.kernel.org%2fpub%2fscm%2flinux%2fkernel%2fgit%2ftorvalds%2flinux.git&data=01%7c01%7ckys%40microsoft.com%7ce2e0622715844b79ad7108d32796ec3c%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ubr4GbBaNS%2ftOz%2buJBk0CL9N0UNG9x2Ti
> -Original Message-
> From: James Bottomley [mailto:james.bottom...@hansenpartnership.com]
> Sent: Friday, February 26, 2016 3:33 PM
> To: KY Srinivasan ; linux-ker...@vger.kernel.org;
> de...@linuxdriverproject.org; oher...@suse.com;
> jbottom...@parallels.com; h...@infradead.org; linux
> -Original Message-
> From: James Bottomley [mailto:james.bottom...@hansenpartnership.com]
> Sent: Thursday, January 28, 2016 7:37 AM
> To: Olaf Hering
> Cc: KY Srinivasan ; Haiyang Zhang
> ; linux-ker...@vger.kernel.org; linux-
> s...@vger.kernel.org
> Subject: Re: [PATCH] storvsc: use
On Fri, 2016-02-26 at 23:22 +, KY Srinivasan wrote:
>
> > -Original Message-
> > From: James Bottomley [mailto:james.bottom...@hansenpartnership.com
> > ]
> > Sent: Friday, February 26, 2016 2:25 PM
> > To: KY Srinivasan ; linux-ker...@vger.kernel.org
> > ;
> > de...@linuxdriverproject
> -Original Message-
> From: James Bottomley [mailto:james.bottom...@hansenpartnership.com]
> Sent: Friday, February 26, 2016 2:25 PM
> To: KY Srinivasan ; linux-ker...@vger.kernel.org;
> de...@linuxdriverproject.org; oher...@suse.com;
> jbottom...@parallels.com; h...@infradead.org; linux
> "Walter" == bugzilla-daemon writes:
Walter> https://bugzilla.kernel.org/show_bug.cgi?id=111341 --- Comment
Walter> #5 from walter59 --- hello,
Walter> bug is still alive on most boards --- changes has has no
Walter> resolved problems.
Please report ahci issues to linux-...@vger.kernel.o
On Fri, 2016-02-26 at 15:45 -0800, K. Y. Srinivasan wrote:
> tree: https://na01.safelinks.protection.outlook.com/?url=https%3a%2
> f%2fgit.kernel.org%2fpub%2fscm%2flinux%2fkernel%2fgit%2ftorvalds%2fli
> nux.git&data=01%7c01%7ckys%40microsoft.com%7ce2e0622715844b79ad7108d3
> 2796ec3c%7c72f988bf86f
> "Gabriel" == Gabriel Krisman Bertazi writes:
Gabriel> Commit d63c7dd5bcb9 ("ipr: Fix out-of-bounds null overwrite")
Gabriel> removed the end of line handling when storing the update_fw
Gabriel> sysfs attribute. This changed the userpace API because it
Gabriel> started refusing writes termi
> "tom" == tom ty89 writes:
Tom,
tom> [root@localhost ~]# sg_opcodes /dev/sdb > /dev/null Report
tom> supported operation codes: Illegal request, invalid opcode
tom> [root@localhost ~]# sg_vpd -p bl /dev/sdb | grep 'write same'
tom> Maximum write same length: 0x0 blocks
"A MAXIMUM WRITE SA
tree:
https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgit.kernel.org%2fpub%2fscm%2flinux%2fkernel%2fgit%2ftorvalds%2flinux.git&data=01%7c01%7ckys%40microsoft.com%7ce2e0622715844b79ad7108d32796ec3c%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ubr4GbBaNS%2ftOz%2buJBk0CL9N0UNG9x2Ti
From: Tom Yan
Example:
[root@localhost ~]# sg_opcodes /dev/sdb > /dev/null
Report supported operation codes: Illegal request, invalid opcode
[root@localhost ~]# sg_vpd -p bl /dev/sdb | grep 'write same'
Maximum write same length: 0x0 blocks
[root@localhost ~]# cat /sys/block/sdb/queue/write_
No I mean I no longer thinks that this condition needs to be inverted.
I just THOUGHT that !scsi_get_vpd_page is true if it DIDN'T get the
page.
On 27 February 2016 at 04:57, James Bottomley
wrote:
> On Sat, 2016-02-27 at 04:32 +0800, Tom Yan wrote:
>> Oh I made a mistake on this one then.
>>
>>
On Fri, 2016-02-26 at 14:52 -0600, Brian King wrote:
> On 02/25/2016 10:54 AM, Gabriel Krisman Bertazi wrote:
> > Commit d63c7dd5bcb9 ("ipr: Fix out-of-bounds null overwrite")
> > removed the
> > end of line handling when storing the update_fw sysfs attribute.
> > This
> > changed the userpace AP
On Sat, 2016-02-27 at 04:32 +0800, Tom Yan wrote:
> Oh I made a mistake on this one then.
>
> Since I send it with another patch, should I resend that alone?
Yes, that's fine. but you need to explain as part of the changelog why
this condition needs inverting because your Subject just says "as pe
On 02/25/2016 10:54 AM, Gabriel Krisman Bertazi wrote:
> Commit d63c7dd5bcb9 ("ipr: Fix out-of-bounds null overwrite") removed the
> end of line handling when storing the update_fw sysfs attribute. This
> changed the userpace API because it started refusing writes terminated
> by a line feed, whic
Oh I made a mistake on this one then.
Since I send it with another patch, should I resend that alone?
On 27 February 2016 at 04:16, James Bottomley
wrote:
> On Sat, 2016-02-27 at 04:07 +0800, tom.t...@gmail.com wrote:
>> From: Tom Yan
>>
>> Signed-off-by: Tom Yan
>>
>> diff --git a/drivers/scs
I wonder if we want to disable write same too, instead of falling back
to SD_MAX_WS10_BLOCKS for either of the WRITE SAME (10) and (16)
opcodes, when they are reported to be supported. If not, should we go
for SD_MAX_WS16_BLOCKS instead when WRITE SAME (16) is supported?
P.S. Please be noted I hav
On Sat, 2016-02-27 at 04:07 +0800, tom.t...@gmail.com wrote:
> From: Tom Yan
>
> Signed-off-by: Tom Yan
>
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> index 1179ec1..951 100644
> --- a/drivers/scsi/sd.c
> +++ b/drivers/scsi/sd.c
> @@ -2786,7 +2786,7 @@ static void sd_read_write_sa
From: Tom Yan
Signed-off-by: Tom Yan
diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
index 1179ec1..951 100644
--- a/drivers/scsi/sd.c
+++ b/drivers/scsi/sd.c
@@ -2786,7 +2786,7 @@ static void sd_read_write_same(struct scsi_disk *sdkp,
unsigned char *buffer)
* CODES is
From: Tom Yan
Example:
[root@localhost ~]# sg_opcodes /dev/sdb > /dev/null
Report supported operation codes: Illegal request, invalid opcode
[root@localhost ~]# sg_vpd -p bl /dev/sdb | grep 'write same'
Maximum write same length: 0x0 blocks
[root@localhost ~]# cat /sys/block/sdb/queue/write_
Hi,
I'd like to participate in LSF/MM and would like to present/discuss
ideas for introducing I/O scheduling support to blk-mq.
Motiviation for this is to be able use scsi-mq even on systems that
have slow (spinning) devices attached to the SCSI stack.
I think the presentation/discussion should
28 matches
Mail list logo
