From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Jan Kara <jack@suse.cz>
Cc: bugzilla-daemon@bugzilla.kernel.org, linux-ext4@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [Bug 203107] New: Bad page map in process during boot
Date: Thu, 4 Apr 2019 16:08:39 +0300 [thread overview]
Message-ID: <20190404130839.5tkpwihuct4mex32@kshutemo-mobl1> (raw)
In-Reply-To: <20190402101613.GF12133@quack2.suse.cz>
On Tue, Apr 02, 2019 at 12:16:13PM +0200, Jan Kara wrote:
> Switching to email...
>
> On Fri 29-03-19 20:46:22, bugzilla-daemon@bugzilla.kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=203107
> >
> > Bug ID: 203107
> > Summary: Bad page map in process during boot
> > Product: File System
> > Version: 2.5
> > Kernel Version: 5.0.5
> > Hardware: All
> > OS: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: normal
> > Priority: P1
> > Component: ext4
> > Assignee: fs_ext4@kernel-bugs.osdl.org
> > Reporter: echto1@gmail.com
> > Regression: No
> >
> > Error occurs randomly at boot after upgrading kernel from 5.0.0 to 5.0.4.
> >
> > https://justpaste.it/387uf
>
> I don't think this is an ext4 error. Sure this is an error in file mapping
> of libblkid.so.1.1.0 (which is handled by ext4) but the filesystem has very
> little to say wrt how or which PTEs are installed. And the problem is that
> invalid PTE (dead000000000100) is present in page tables. So this looks
> more like a problem in MM itself. Adding MM guys to CC.
0xdead000000000100 and 0xdead000000000200 are LIST_POISON1 and
LIST_POISON2 repectively. Have no idea how would they end up in page table.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2019-04-04 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-203107-13602@https.bugzilla.kernel.org/>
2019-04-02 10:16 ` Jan Kara
2019-04-04 13:08 ` Kirill A. Shutemov [this message]
2019-04-04 14:10 ` Vlastimil Babka
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=20190404130839.5tkpwihuct4mex32@kshutemo-mobl1 \
--to=kirill@shutemov.name \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.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