From: Jan Kara <jack@suse.cz>
To: Meelis Roos <mroos@linux.ee>
Cc: Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
linux-alpha@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org, linux-mm@kvack.org
Subject: Re: ext4 corruption on alpha with 4.20.0-09062-gd8372ba8ce28
Date: Wed, 20 Feb 2019 10:48:13 +0100 [thread overview]
Message-ID: <20190220094813.GA27474@quack2.suse.cz> (raw)
In-Reply-To: <d444f653-9b99-5e9b-3b47-97f824c29b0e@linux.ee>
On Wed 20-02-19 08:31:05, Meelis Roos wrote:
> > Could
> > https://lore.kernel.org/linux-mm/20190219123212.29838-1-larper@axis.com/T/#u
> > be relevant?
>
> Tried it, still broken.
OK, I didn't put too much hope into this patch as you see filesystem
metadata corruption so icache/dcache coherency issues seemed unlikely.
Still good that you've tried so that we are sure.
> I wrote:
>
> > But my kernel config had memory compaction (that turned on page migration) and
> > bounce buffers. I do not remember why I found them necessary but I will try
> > without them.
>
> First, I found out that both the problematic alphas had memory compaction and
> page migration and bounce buffers turned on, and working alphas had them off.
>
> Next, turing off these options makes the problematic alphas work.
OK, thanks for testing! Can you narrow down whether the problem is due to
CONFIG_BOUNCE or CONFIG_MIGRATION + CONFIG_COMPACTION? These are two
completely different things so knowing where to look will help. Thanks!
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2019-02-20 9:48 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
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 [this message]
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=20190220094813.GA27474@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mroos@linux.ee \
--cc=tytso@mit.edu \
--cc=willy@infradead.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