linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jack Wang <jack.wang.usish@gmail.com>
To: shapiro.gregory@gmail.com
Cc: hch@infradead.org, jnicklin@blockbridge.com,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	gregory.shapiro@kaminario.com
Subject: Re: BUG: aio/direct-io data corruption in 4.7
Date: Fri, 9 Nov 2018 16:44:12 +0100	[thread overview]
Message-ID: <CA+res+QuZKrWN=CPafoxF+nB1HaDygbcoiDcY3-Q=EkwBXedfw@mail.gmail.com> (raw)
In-Reply-To: <CAAGb-1eLHwRy2L5tp+skWdV5zJ7jfCwTe-1UnJq_n5yjQfdJug@mail.gmail.com>

Gregory Shapiro <shapiro.gregory@gmail.com> 于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 storage).
> The issue was caused because of faulty hardware, but the real problem
> is I got a correct number of bytes in io_getevents thus couldn't
> recognize it correctly the error.
> Looking at the /var/log/messages and  I saw the following errors in
> time of coruption:
Thanks for the info, Gregory.

I noticed guys from Amazon pushing the fix to upstream:
https://lore.kernel.org/patchwork/patch/1008443/
I hope it will be in upstream soon.


Regards,
Jack Wang

  reply	other threads:[~2018-11-09 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 15:16 BUG: aio/direct-io data corruption in 4.7 Gregory Shapiro
2018-11-06  7:28 ` Jack Wang
2018-11-06 11:31   ` Gregory Shapiro
2018-11-09 15:44     ` Jack Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-12 18:38 Jonathan Nicklin
2016-09-21 14:15 ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+res+QuZKrWN=CPafoxF+nB1HaDygbcoiDcY3-Q=EkwBXedfw@mail.gmail.com' \
    --to=jack.wang.usish@gmail.com \
    --cc=gregory.shapiro@kaminario.com \
    --cc=hch@infradead.org \
    --cc=jnicklin@blockbridge.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shapiro.gregory@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).