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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAAGb-1fPZsJRqa4C3zDiatqE2sPAV8m-pGBoG+z=3nAd+Koj-A@mail.gmail.com>
Date:   Mon, 5 Nov 2018 17:16:21 +0200
From:   Gregory Shapiro <shapiro.gregory@...il.com>
To:     hch@...radead.org, jnicklin@...ckbridge.com
Cc:     linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        gregory.shapiro@...inario.com,
        Gregory Shapiro <shapiro.gregory@...il.com>
Subject: Re: BUG: aio/direct-io data corruption in 4.7

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 issue found
in direct-io.c mentioned the bellow thread.
https://lore.kernel.org/lkml/20160921141539.GA17898@infradead.org/
Is there a reason proposed patch didn't apply to the kernel?
When can I expect it to be applied?
Thanks,
 Gregory