https://bugzilla.kernel.org/show_bug.cgi?id=23
Brent (bzipiti...@gmail.com) changed:
What|Removed |Added
Kernel Version|2.6.27 |2.6.26
--
You are
https://bugzilla.kernel.org/show_bug.cgi?id=23
--- Comment #8 from Brent (bzipiti...@gmail.com) ---
Created attachment 276699
--> https://bugzilla.kernel.org/attachment.cgi?id=276699=edit
2.6.26 dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=23
--- Comment #7 from Brent (bzipiti...@gmail.com) ---
Created attachment 276697
--> https://bugzilla.kernel.org/attachment.cgi?id=276697=edit
2.6.25 dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=23
--- Comment #6 from Brent (bzipiti...@gmail.com) ---
This turned out to be way harder than it should have been, thanks to a serious
problem with "make oldconfig". I installed OpenSUSE 11 and took its working
2.6.25 configuration, copied it into
Bart,
> This patch series addresses the complaints reported by multiple static
> source code analysis tools about the mpt3sas source code. Please
> consider these patches for kernel v4.19.
Applied to 4.19/scsi-queue. Thank you!
--
Martin K. Petersen Oracle Linux Engineering
Don,
> The changes are:
>
> - improve handling for sync requests
>ensure controller is ready for requests
> - improve-error-checking-for-sync-requests
>detect rare error cases for synchronous requests
> - add more supported devices
> - fix critical ARM issue reading PQI index
On Mon, 2018-06-18 at 13:23 -0500, Don Brace wrote:
> From: Kevin Barnett
>
> - use the readl() kernel function to read all index
> registers. For ARM systems, this function includes a
> read memory barrier that eliminates ci/pi corruption.
>
> Reviewed-by: Scott Benesh
> Reviewed-by:
David,
> SPC5r17 states that the contents of the ADDITIONAL LENGTH field are not
> altered based on the allocation length, so always calculate and pack the
> full key list length even if the list itself is truncated.
>
> According to Maged:
> Yes it fixes the "Storage Spaces Persistent
Christoph,
> It was reported that some devices report an OPTIMAL TRANSFER LENGTH of
> 0x blocks. That looks bogus, especially for a device with a
> 4096-byte physical block size.
>
> Ignore OPTIMAL TRANSFER LENGTH if it is not a multiple of the device's
> reported physical block size.
Did
SPC5r17 states that the contents of the ADDITIONAL LENGTH field are not
altered based on the allocation length, so always calculate and pack the
full key list length even if the list itself is truncated.
According to Maged:
Yes it fixes the "Storage Spaces Persistent Reservation" test in the
On Mon, Jun 18, 2018 at 01:41:48PM +0200, David Disseldorp wrote:
> On Mon, 18 Jun 2018 04:12:17 -0700, Christoph Hellwig wrote:
>
> > On Sun, Jun 17, 2018 at 12:40:56PM +0800, Zhu Lingshan wrote:
> > > Hello Mike and Christoph，
> > > Thanks Mike's comment inspired me, if I understand this
Good Day;
Dear Respectful One,
I am SALINAS ROMANS from France. Please go through below my mail and
see if you can Assist for Our mutual benefit, My late Father was a
serving director of the Cocoa exporting board in lvory coast until his
death.
He died in motor accident one week after his trip
cc'ing the SCSI list, as it doesn't look like anything is making it
through target-devel nowadays...
https://patchwork.kernel.org/patch/10448059/
Cheers, David
On Tue, 5 Jun 2018 12:00:25 +0200, David Disseldorp wrote:
> SPC5r17 states that the contents of the ADDITIONAL LENGTH field are not
>
The size of free_list_lock and free_list is num_possible_cpus,
and cpu id returned by get_cpu() maybe bigger than
num_possible_cpus, due to the non-continuous cpu ids.
Signed-off-by: Li RongQing
Signed-off-by: Wang Li
---
drivers/scsi/bnx2fc/bnx2fc_io.c | 2 +-
1 file changed, 1 insertion(+),
14 matches
Mail list logo
