From: Meelis Roos <mroos@linux.ee>
To: Jan Kara <jack@suse.cz>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
linux-alpha@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org
Subject: Re: ext4 corruption on alpha with 4.20.0-09062-gd8372ba8ce28
Date: Mon, 18 Feb 2019 14:37:24 +0200 [thread overview]
Message-ID: <7ffcadd5-47b3-e44a-bd18-7e9f1a636f8d@linux.ee> (raw)
In-Reply-To: <20190218120209.GC20919@quack2.suse.cz>
> Hum, weird. I have hard time understanding how that change could be causing
> fs corruption on Aplha but OTOH it is not completely unthinkable. With this
> commit we may migrate some block device pages we were not able to migrate
> previously and that could be causing some unexpected issue. I'll look into
> this.
To make things more interesting, it does not happen on any alpha but only one subarch
so far: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1889207.html
is my original bug report.
--
Meelis Roos <mroos@linux.ee>
next prev parent reply other threads:[~2019-02-18 12:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fb63a4d0-d124-21c8-7395-90b34b57c85a@linux.ee>
2019-02-10 20:27 ` ext4 corruption on alpha with 4.20.0-09062-gd8372ba8ce28 Meelis Roos
2019-02-15 16:59 ` Meelis Roos
2019-02-16 17:45 ` Theodore Y. Ts'o
2019-02-16 22:29 ` Meelis Roos
2019-02-18 12:02 ` Jan Kara
2019-02-18 12:37 ` Meelis Roos [this message]
2019-02-19 12:17 ` Meelis Roos
2019-02-19 13:20 ` Jan Kara
2019-02-19 13:49 ` Meelis Roos
2019-02-19 14:44 ` Matthew Wilcox
2019-02-20 6:31 ` Meelis Roos
2019-02-20 9:48 ` Jan Kara
2019-02-20 23:23 ` Meelis Roos
2019-02-21 13:29 ` Jan Kara
2022-08-25 15:05 ` matoro
2022-08-26 10:55 ` Jan Kara
2022-08-26 11:04 ` Vlastimil Babka
2022-08-26 16:16 ` matoro
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=7ffcadd5-47b3-e44a-bd18-7e9f1a636f8d@linux.ee \
--to=mroos@linux.ee \
--cc=jack@suse.cz \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).