Displaying 4 results from an estimated 4 matches for "rglite4kwmu8_smb_2".
2020 Apr 30
3
io_uring cause data corruption
On 2020-04-29 00:40, Jeremy Allison via samba wrote:
> On Mon, Apr 27, 2020 at 11:21:35PM +0200, A L wrote:
>> I set up the following test case:
>> * Linux 5.7-rc3 (with the patch from previous mail)
>> * samba-4.12.1
>> * gcc-9.3.0
>> * liburing-0.6
>> * glibc-2.30-r8
>>
>> =================================
>> Test 1)
>> Copy 10 10GB
2020 Apr 30
2
io_uring cause data corruption
...t; At position 0x800000 the zeroes ended and correct data continued. To me it
> sound like some wrong memory is copied somehow.
>
> These two files shows the difference as shown in a hex-editor.
> https://paste.tnonline.net/files/MO1FJvDOG6E8_smb_1
> https://paste.tnonline.net/files/Rglite4KWmU8_smb_2
Is it always the same area in the file that is corrupt ?
The fact that it's on a 4K page-aligned boundary is
interesting. If you can corrolate I'd love to see
the SMB2 traffic on the wire that corresponds to the
corrupted data write/read.
2020 Apr 30
0
io_uring cause data corruption
...contain only binary
zero. At position 0x800000 the zeroes ended and correct data continued.
To me it sound like some wrong memory is copied somehow.
These two files shows the difference as shown in a hex-editor.
https://paste.tnonline.net/files/MO1FJvDOG6E8_smb_1
https://paste.tnonline.net/files/Rglite4KWmU8_smb_2
I will redo the tests with different Windows clients and see if that
shows different results.
2020 May 01
0
io_uring cause data corruption
...0000 the zeroes ended and correct data continued. To me it
>> sound like some wrong memory is copied somehow.
>>
>> These two files shows the difference as shown in a hex-editor.
>> https://paste.tnonline.net/files/MO1FJvDOG6E8_smb_1
>> https://paste.tnonline.net/files/Rglite4KWmU8_smb_2
> Is it always the same area in the file that is corrupt ?
> The fact that it's on a 4K page-aligned boundary is
> interesting. If you can corrolate I'd love to see
> the SMB2 traffic on the wire that corresponds to the
> corrupted data write/read.
>
Hi again,
It is not a...