Thomas Meyer
2017-05-07 20:06:33 UTC
Hi,
with the current rw/linux-next I see a lot of those:
Mai 07 22:01:34 bifrst kernel: ------------[ cut here ]------------
Mai 07 22:01:34 bifrst kernel: WARNING: CPU: 0 PID: 505 at mm/mmap.c:1112 vma_merge+0x323/0x3c0
Mai 07 22:01:34 bifrst kernel: Modules linked in:
Mai 07 22:01:34 bifrst kernel: CPU: 0 PID: 505 Comm: less Tainted: G W 4.11.0-00006-gce45860 #279
Mai 07 22:01:34 bifrst kernel: Stack:
Mai 07 22:01:34 bifrst kernel: 9e69da50 600c5bf4 00000009 00000000
Mai 07 22:01:34 bifrst kernel: 6015c8e6 00000000 9e69da60 604f536c
Mai 07 22:01:34 bifrst kernel: 9e69dac0 600671ae 45800000000 601a38d3
Mai 07 22:01:34 bifrst kernel: Call Trace:
Mai 07 22:01:34 bifrst kernel: [<601a38d3>] ? vma_merge+0x323/0x3c0
Mai 07 22:01:34 bifrst kernel: [<6015c8e6>] ? printk+0x0/0x94
Mai 07 22:01:34 bifrst kernel: [<60044ac9>] show_stack+0x129/0x190
Mai 07 22:01:34 bifrst kernel: [<600c5bf4>] ? dump_stack_print_info+0xe4/0xf0
Mai 07 22:01:34 bifrst kernel: [<6015c8e6>] ? printk+0x0/0x94
Mai 07 22:01:34 bifrst kernel: [<604f536c>] dump_stack+0x2a/0x2e
Mai 07 22:01:34 bifrst kernel: [<600671ae>] __warn+0x11e/0x150
Mai 07 22:01:34 bifrst kernel: [<601a38d3>] ? vma_merge+0x323/0x3c0
Mai 07 22:01:34 bifrst kernel: [<6006732f>] warn_slowpath_null+0x1f/0x30
Mai 07 22:01:34 bifrst kernel: [<601a38d3>] vma_merge+0x323/0x3c0
Mai 07 22:01:34 bifrst kernel: [<601a5140>] ? may_expand_vm+0x0/0x170
Mai 07 22:01:34 bifrst kernel: [<601a781d>] mprotect_fixup+0x14d/0x2e0
Mai 07 22:01:34 bifrst kernel: [<601de54c>] setup_arg_pages+0x10c/0x470
Mai 07 22:01:34 bifrst kernel: [<6083cb34>] ? _raw_spin_unlock+0x34/0x40
Mai 07 22:01:34 bifrst kernel: [<604fe410>] ? memcmp+0x0/0x50
Mai 07 22:01:34 bifrst kernel: [<60837704>] ? mutex_unlock+0x14/0x20
Mai 07 22:01:34 bifrst kernel: [<602545aa>] load_elf_binary+0x47a/0xfe0
Mai 07 22:01:34 bifrst kernel: [<600ba966>] ? lock_release+0x736/0x7f0
Mai 07 22:01:34 bifrst kernel: [<600ba1e3>] ? lock_acquire+0x203/0x250
Mai 07 22:01:34 bifrst kernel: [<600b4c3e>] ? lock_acquired+0x4ae/0x530
any idea what is going on here?
with the current rw/linux-next I see a lot of those:
Mai 07 22:01:34 bifrst kernel: ------------[ cut here ]------------
Mai 07 22:01:34 bifrst kernel: WARNING: CPU: 0 PID: 505 at mm/mmap.c:1112 vma_merge+0x323/0x3c0
Mai 07 22:01:34 bifrst kernel: Modules linked in:
Mai 07 22:01:34 bifrst kernel: CPU: 0 PID: 505 Comm: less Tainted: G W 4.11.0-00006-gce45860 #279
Mai 07 22:01:34 bifrst kernel: Stack:
Mai 07 22:01:34 bifrst kernel: 9e69da50 600c5bf4 00000009 00000000
Mai 07 22:01:34 bifrst kernel: 6015c8e6 00000000 9e69da60 604f536c
Mai 07 22:01:34 bifrst kernel: 9e69dac0 600671ae 45800000000 601a38d3
Mai 07 22:01:34 bifrst kernel: Call Trace:
Mai 07 22:01:34 bifrst kernel: [<601a38d3>] ? vma_merge+0x323/0x3c0
Mai 07 22:01:34 bifrst kernel: [<6015c8e6>] ? printk+0x0/0x94
Mai 07 22:01:34 bifrst kernel: [<60044ac9>] show_stack+0x129/0x190
Mai 07 22:01:34 bifrst kernel: [<600c5bf4>] ? dump_stack_print_info+0xe4/0xf0
Mai 07 22:01:34 bifrst kernel: [<6015c8e6>] ? printk+0x0/0x94
Mai 07 22:01:34 bifrst kernel: [<604f536c>] dump_stack+0x2a/0x2e
Mai 07 22:01:34 bifrst kernel: [<600671ae>] __warn+0x11e/0x150
Mai 07 22:01:34 bifrst kernel: [<601a38d3>] ? vma_merge+0x323/0x3c0
Mai 07 22:01:34 bifrst kernel: [<6006732f>] warn_slowpath_null+0x1f/0x30
Mai 07 22:01:34 bifrst kernel: [<601a38d3>] vma_merge+0x323/0x3c0
Mai 07 22:01:34 bifrst kernel: [<601a5140>] ? may_expand_vm+0x0/0x170
Mai 07 22:01:34 bifrst kernel: [<601a781d>] mprotect_fixup+0x14d/0x2e0
Mai 07 22:01:34 bifrst kernel: [<601de54c>] setup_arg_pages+0x10c/0x470
Mai 07 22:01:34 bifrst kernel: [<6083cb34>] ? _raw_spin_unlock+0x34/0x40
Mai 07 22:01:34 bifrst kernel: [<604fe410>] ? memcmp+0x0/0x50
Mai 07 22:01:34 bifrst kernel: [<60837704>] ? mutex_unlock+0x14/0x20
Mai 07 22:01:34 bifrst kernel: [<602545aa>] load_elf_binary+0x47a/0xfe0
Mai 07 22:01:34 bifrst kernel: [<600ba966>] ? lock_release+0x736/0x7f0
Mai 07 22:01:34 bifrst kernel: [<600ba1e3>] ? lock_acquire+0x203/0x250
Mai 07 22:01:34 bifrst kernel: [<600b4c3e>] ? lock_acquired+0x4ae/0x530
any idea what is going on here?