linux-ext4 - [Bug 203107] Bad page map in process during boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <bug-203107-13602-OelBiVaBKD@https.bugzilla.kernel.org/>
Date:   Thu, 04 Apr 2019 14:23:50 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 203107] Bad page map in process during boot

https://bugzilla.kernel.org/show_bug.cgi?id=203107

--- Comment #4 from Vlastimil Babka (vbabka@...e.cz) ---
On 4/4/19 3:08 PM, Kirill A. Shutemov wrote:
> 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@...zilla.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@...nel-bugs.osdl.org
>>>           Reporter: echto1@...il.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.

It's possible that CONFIG_DEBUG_LIST could catch the issue. Between
5.0.0 to 5.0.4 it should be also relatively easy to bisect with the
stable git tree [1], although if it happens randomly, you need to
perform enough attempts to accurately determine which commit is "good".

[1] git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git

-- 
You are receiving this mail because:
You are watching the assignee of the bug.