linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jane Chu <jane.chu@oracle.com>
To: "Luck, Tony" <tony.luck@intel.com>,
	Borislav Petkov <bp@alien8.de>,
	"djwong@kernel.org" <djwong@kernel.org>
Cc: "x86@kernel.org" <x86@kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Is it possible to corrupt disk when writeback page with undetected UE?
Date: Thu, 15 Sep 2022 22:36:30 +0000	[thread overview]
Message-ID: <44fe39d7-ac92-0abc-220b-5f5875faf3a9@oracle.com> (raw)

Hi,

Suppose there is a UE in a DRAM page that is backed by a disk file.
The UE hasn't been reported to the kernel, but low level firmware 
initiated scrubbing has already logged the UE.

The page is then dirtied by a write, although the write clearly failed,
it didn't trigger an MCE.

And without a subsequent read from the page, at some point, the page is 
written back to the disk, leaving a PAGE_SIZE of zeros in the targeted 
disk blocks.

Is this mode of disk corruption possible?

Thanks a lot!
-jane

             reply	other threads:[~2022-09-15 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15 22:36 Jane Chu [this message]
2022-09-15 22:50 ` Is it possible to corrupt disk when writeback page with undetected UE? Luck, Tony
2022-09-16  0:26   ` Jane Chu
2022-09-16  0:30     ` Yang Shi
2022-09-16  0:51       ` Jane Chu
2022-09-16 16:17     ` Luck, Tony
2022-09-16 19:26       ` Jane Chu

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=44fe39d7-ac92-0abc-220b-5f5875faf3a9@oracle.com \
    --to=jane.chu@oracle.com \
    --cc=bp@alien8.de \
    --cc=djwong@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    /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).