Re: BUG: aio/direct-io data corruption in 4.7

2018-11-09 Thread Jack Wang
Gregory Shapiro 于2018年11月6日周二 下午12:31写道: > > Hi Jack, > I tested it in 4.9.102 and I checked the latest code from elixir > (versions 4.19 and 4.20) and the error in code is still present there. > More on the scenario and the bug: > I experienced data corruption in my application (nvme based storag

Re: BUG: aio/direct-io data corruption in 4.7

2018-11-06 Thread Gregory Shapiro
Hi Jack, I tested it in 4.9.102 and I checked the latest code from elixir (versions 4.19 and 4.20) and the error in code is still present there. More on the scenario and the bug: I experienced data corruption in my application (nvme based storage). The issue was caused because of faulty hardware, b

Re: BUG: aio/direct-io data corruption in 4.7

2018-11-05 Thread Jack Wang
Gregory Shapiro 于2018年11月5日周一 下午4:19写道: > > Hello, my name is Gregory Shapiro and I am a newbie on this list. > I recently encountered data corruption as I got a kernel to > acknowledge write ("io_getevents" system call with a correct number of > bytes) but undergoing write to disk failed. > After

Re: BUG: aio/direct-io data corruption in 4.7

2018-11-05 Thread Gregory Shapiro
Hello, my name is Gregory Shapiro and I am a newbie on this list. I recently encountered data corruption as I got a kernel to acknowledge write ("io_getevents" system call with a correct number of bytes) but undergoing write to disk failed. After investigating the problem I found it is identical to

Re: BUG: aio/direct-io data corruption in 4.7

2016-09-21 Thread Christoph Hellwig
Hi Jonathan, please keep linux-fsdevel on the Cc list for something like, and if you already track down a commit the author of that commit. > Description: "fs: simplify the generic_write_sync prototype" > Committed: Apr 7, 2016 > Hash: e259221763a40403d5bb232209998e8c45804ab8 > Affects: 4.7-rc1 -