linux-kernel - 4.11.0-rc2 BUG: Bad page map in process libinput-device

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>] [day] [month] [year] [list]

Date:   Mon, 13 Mar 2017 13:19:00 +1030
From:   Arthur Marsh <arthur.marsh@...ernode.on.net>
To:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: 4.11.0-rc2 BUG: Bad page map in process libinput-device

I've had no issues building the 4.11.0-rc1+ kernels on x86_64 until some 
commits in the last 24 hours, that resulted in:

[   18.746569] BUG: Bad page map in process libinput-device 
pte:00003f90 pmd:22
0910067
[   18.746757] addr:00007efd31d00000 vm_flags:08000070 anon_vma: 
  (null)
  mapping:ffff9e282db48320 index:1a0
[   18.747051] file:libffi.so.6.0.4 fault:ext4_filemap_fault [ext4] 
mmap:ext4_fi
le_mmap [ext4] readpage:ext4_readpage [ext4]
[   18.747243] CPU: 1 PID: 548 Comm: libinput-device Not tainted 
4.11.0-rc2 #2635
[   18.747370] Hardware name: System manufacturer System Product 
Name/M3A78 PRO, BIOS 1701    01/27/2011
[   18.747528] Call Trace:
[   18.747587]  ? dump_stack+0x5c/0x84
[   18.747656]  ? print_bad_pte+0x1f8/0x2e0
[   18.747731]  ? __dec_node_state+0x58/0xc0
[   18.747809]  ? lock_page_memcg+0x11/0x80
[   18.747884]  ? vm_normal_page+0x91/0xa0
[   18.747959]  ? unmap_page_range+0x575/0x920
[   18.748041]  ? unmap_vmas+0x4c/0xa0
[   18.748109]  ? exit_mmap+0x9b/0x160
[   18.748179]  ? mmput+0x4d/0x150
[   18.748240]  ? do_exit+0x28f/0xb90
[   18.748308]  ? vfs_write+0x16b/0x1b0
[   18.748376]  ? do_group_exit+0x3a/0xa0
[   18.748447]  ? SyS_exit_group+0x10/0x10
[   18.748521]  ? entry_SYSCALL_64_fastpath+0x1e/0xad
[   18.748658] Disabling lock debugging due to kernel taint

Is there a way to run git bisect to start with the git head of about 
24-48 hours previously (known good) and the current git head as bad?

I can supply config/build options/full dmesg and run tests.

Arthur.