Skip to contentSkip to conversation

fs: proc: gpf in find_entry

DISCUSSION Sasha Levin 3 participants 8 messages Dec 22, 2014 – Dec 23, 2014 VFS

lore
Share & tools
lore
#0 lore raw

Hi all,

While fuzzing with trinity inside a KVM tools guest running the latest -next kernel, I've stumbled on the following spew:

[ 2015.960381] general protection fault: 0000 [#1] PREEMPT SMP KASAN
[ 2015.961912] Dumping ftrace buffer:
[ 2015.962803]    (ftrace buffer empty)
[ 2015.963370] Modules linked in:
[ 2015.963895] CPU: 1 PID: 16983 Comm: trinity-c126 Not tainted 3.18.0-next-20141219-sasha-00047-gaab33f6-dirty #1627
[ 2015.965991] task: ffff88080e478000 ti: ffff88080e474000 task.ti: ffff88080e474000
[ 2015.968196] RIP: find_entry (fs/proc/proc_sysctl.c:95)
[ 2015.970534] RSP: 0018:ffff88080e4779d8  EFLAGS: 00010246
[ 2015.970534] RAX: 0000000000000000 RBX: ffff88000003a960 RCX: 0000000000000073
[ 2015.970534] RDX: 1ffff10101c8f3c4 RSI: 0000000000000000 RDI: ffff88080e479e20
[ 2015.970534] RBP: ffff88080e477a28 R08: 0000000000000066 R09: 0000000000000073
[ 2015.970534] R10: ffffda0017d55630 R11: dfffe90000000000 R12: ffff88005fc644b8
[ 2015.970534] R13: dfffe90000000000 R14: ffffffff92464884 R15: 0000000000000000
[ 2015.970534] FS:  00007f9cd6c6f700(0000) GS:ffff8800c2200000(0000) knlGS:0000000000000000
[ 2015.970534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2015.970534] CR2: 00007f9cd0b9c000 CR3: 00000008193fb000 CR4: 00000000000006a0
[ 2015.970534] DR0: ffffffffff000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 2015.970534] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
[ 2015.970534] Stack:
[ 2015.970534]  ffff88080e477a28 ffff88080e477a50 00000003beaab0c0 ffff8800beaab0f8
[ 2015.970534]  0000000000000001 ffff8800beaab0f8 ffff8800beaab0c0 ffff8806079af638
[ 2015.970534]  0000000000000003 ffff88045f3cc000 ffff88080e477a88 ffffffff81c4e0ef
[ 2015.970534] Call Trace:
[ 2015.970534] proc_sys_lookup (fs/proc/proc_sysctl.c:303 fs/proc/proc_sysctl.c:452)
[ 2015.970534] ? d_alloc (fs/dcache.c:1499)
[ 2015.970534] lookup_real (fs/namei.c:1371)
[ 2015.970534] __lookup_hash (fs/namei.c:1390)
[ 2015.970534] link_path_walk (fs/namei.c:1496 fs/namei.c:1576 fs/namei.c:1830)
[ 2015.970534] ? preempt_count_sub (kernel/sched/core.c:2620)
[ 2015.970534] ? get_parent_ip (kernel/sched/core.c:2564)
[ 2015.970534] ? get_parent_ip (kernel/sched/core.c:2564)
[ 2015.970534] ? __cmpxchg_double_slab.isra.4 (./arch/x86/include/asm/preempt.h:95 include/linux/bit_spinlock.h:81 mm/slub.c:346 mm/slub.c:386)
[ 2015.970534] path_init (fs/namei.c:1947)
[ 2015.970534] ? deactivate_slab (include/linux/spinlock.h:349 mm/slub.c:1945)
[ 2015.970534] path_lookupat (fs/namei.c:1989)
[ 2015.970534] ? alloc_debug_processing (mm/slub.c:1044)
[ 2015.970534] filename_lookup (fs/namei.c:2025)
[ 2015.970534] kern_path_create (fs/namei.c:3309)
[ 2015.970534] ? getname_flags (fs/namei.c:159)
[ 2015.970534] ? vtime_account_user (kernel/sched/cputime.c:701)
[ 2015.970534] user_path_create (fs/namei.c:3381)
[ 2015.970534] SyS_mknod (fs/namei.c:3443 fs/namei.c:3431 fs/namei.c:3475 fs/namei.c:3473)
[ 2015.970534] tracesys_phase2 (arch/x86/kernel/entry_64.S:529)
[ 2015.970534] Code: e8 03 42 80 3c 28 00 0f 85 ff 01 00 00 4c 8b 7b 18 4d 85 ff 0f 84 de 01 00 00 41 f6 c7 07 0f 85 d4 01 00 00 4c 89 f8 48 c1 e8 03 <42> 80 3c 28 00 0f 85 b5 01 00 00 4d 8b 37 4d 85 ff 0f 84 55 02
All code
========
   0:	e8 03 42 80 3c       	callq  0x3c804208
   5:	28 00                	sub    %al,(%rax)
   7:	0f 85 ff 01 00 00    	jne    0x20c
   d:	4c 8b 7b 18          	mov    0x18(%rbx),%r15
  11:	4d 85 ff             	test   %r15,%r15
  14:	0f 84 de 01 00 00    	je     0x1f8
  1a:	41 f6 c7 07          	test   $0x7,%r15b
  1e:	0f 85 d4 01 00 00    	jne    0x1f8
  24:	4c 89 f8             	mov    %r15,%rax
  27:	48 c1 e8 03          	shr    $0x3,%rax
  2b:*	42 80 3c 28 00       	cmpb   $0x0,(%rax,%r13,1)		<-- trapping instruction
  30:	0f 85 b5 01 00 00    	jne    0x1eb
  36:	4d 8b 37             	mov    (%r15),%r14
  39:	4d 85 ff             	test   %r15,%r15
  3c:	0f                   	.byte 0xf
  3d:	84 55 02             	test   %dl,0x2(%rbp)
	...

Code starting with the faulting instruction
===========================================

   0:	42 80 3c 28 00       	cmpb   $0x0,(%rax,%r13,1)
   5:	0f 85 b5 01 00 00    	jne    0x1c0
   b:	4d 8b 37             	mov    (%r15),%r14
   e:	4d 85 ff             	test   %r15,%r15
  11:	0f                   	.byte 0xf
  12:	84 55 02             	test   %dl,0x2(%rbp)
	...
[ 2015.970534] RIP find_entry (fs/proc/proc_sysctl.c:95)
[ 2015.970534]  RSP <ffff88080e4779d8>
[ 2016.028073] ---[ end trace 142d37d0fb80aa87 ]---
[ 2016.028925] Kernel panic - not syncing: Fatal exception
[ 2016.030263] Dumping ftrace buffer:
[ 2016.030847]    (ftrace buffer empty)
[ 2016.031399] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 2016.032890] Rebooting in 1 seconds..

Thanks,
Sasha

#1 lore raw

2014-12-22 17:37 GMT+03:00 Sasha Levin <[email protected]>:

Quoted 6 lines

Hi all,

While fuzzing with trinity inside a KVM tools guest running the latest -next kernel, I've stumbled on the following spew:

[ 2015.960381] general protection fault: 0000 [#1] PREEMPT SMP KASAN

Actually this is NULL-ptr dereference. Since you are using kasan with inline instrumentation
NULL-ptr deref transforms into GPF.

Quoted 5 lines
[ 2015.970534] RAX: 0000000000000000 RBX: ffff88000003a960 RCX: 0000000000000073
[ 2015.970534] RDX: 1ffff10101c8f3c4 RSI: 0000000000000000 RDI: ffff88080e479e20
[ 2015.970534] RBP: ffff88080e477a28 R08: 0000000000000066 R09: 0000000000000073
[ 2015.970534] R10: ffffda0017d55630 R11: dfffe90000000000 R12: ffff88005fc644b8
[ 2015.970534] R13: dfffe90000000000 R14: ffffffff92464884 R15: 0000000000000000

[...]

Quoted 13 lines

All code
========

   0:   e8 03 42 80 3c          callq  0x3c804208
   5:   28 00                   sub    %al,(%rax)
   7:   0f 85 ff 01 00 00       jne    0x20c
   d:   4c 8b 7b 18             mov    0x18(%rbx),%r15
  11:   4d 85 ff                test   %r15,%r15
  14:   0f 84 de 01 00 00       je     0x1f8
  1a:   41 f6 c7 07             test   $0x7,%r15b
  1e:   0f 85 d4 01 00 00       jne    0x1f8
  24:   4c 89 f8                mov    %r15,%rax
  27:   48 c1 e8 03             shr    $0x3,%rax
  2b:*  42 80 3c 28 00          cmpb   $0x0,(%rax,%r13,1)               <-- trapping instruction

Three commands above are result of KASAN's instrumentation. They check shadow for address in %r15:

     if (*((%r15 >> 3) + kasan_shadow_offset)
Quoted 2 lines
  30:   0f 85 b5 01 00 00       jne    0x1eb
  36:   4d 8b 37                mov    (%r15),%r14

And here is memory access, that KASAN checking.

#2 lore raw
Quoted 37 lines · Andrey Ryabinin

2014-12-22 17:37 GMT+03:00 Sasha Levin <[email protected]>:

Quoted 6 lines

Hi all,

While fuzzing with trinity inside a KVM tools guest running the latest -next kernel, I've stumbled on the following spew:

[ 2015.960381] general protection fault: 0000 [#1] PREEMPT SMP KASAN

Actually this is NULL-ptr dereference. Since you are using kasan with inline instrumentation
NULL-ptr deref transforms into GPF.

Quoted 5 lines
[ 2015.970534] RAX: 0000000000000000 RBX: ffff88000003a960 RCX: 0000000000000073
[ 2015.970534] RDX: 1ffff10101c8f3c4 RSI: 0000000000000000 RDI: ffff88080e479e20
[ 2015.970534] RBP: ffff88080e477a28 R08: 0000000000000066 R09: 0000000000000073
[ 2015.970534] R10: ffffda0017d55630 R11: dfffe90000000000 R12: ffff88005fc644b8
[ 2015.970534] R13: dfffe90000000000 R14: ffffffff92464884 R15: 0000000000000000

[...]

Quoted 13 lines

All code
========

   0:   e8 03 42 80 3c          callq  0x3c804208
   5:   28 00                   sub    %al,(%rax)
   7:   0f 85 ff 01 00 00       jne    0x20c
   d:   4c 8b 7b 18             mov    0x18(%rbx),%r15
  11:   4d 85 ff                test   %r15,%r15
  14:   0f 84 de 01 00 00       je     0x1f8
  1a:   41 f6 c7 07             test   $0x7,%r15b
  1e:   0f 85 d4 01 00 00       jne    0x1f8
  24:   4c 89 f8                mov    %r15,%rax
  27:   48 c1 e8 03             shr    $0x3,%rax
  2b:*  42 80 3c 28 00          cmpb   $0x0,(%rax,%r13,1)               <-- trapping instruction

Three commands above are result of KASAN's instrumentation. They check shadow for address in %r15:

Quoted 7 lines
     if (*((%r15 >> 3) + kasan_shadow_offset)
Quoted 2 lines
  30:   0f 85 b5 01 00 00       jne    0x1eb
  36:   4d 8b 37                mov    (%r15),%r14

And here is memory access, that KASAN checking.

Then frankly I suspect this is a KASAN bug.

These two instructions:

Quoted 2 lines
Quoted 2 lines
  11:   4d 85 ff                test   %r15,%r15
  14:   0f 84 de 01 00 00       je     0x1f8

Should prevent a NULL %r15 value from ever reaching the trapping instruction.

What other horrible things does KASAN do to the machine code?

Eric

#3 lore raw

2014-12-22 18:51 GMT+03:00 Eric W. Biederman <[email protected]>:

Quoted 42 lines
Quoted 40 lines · Andrey Ryabinin

2014-12-22 17:37 GMT+03:00 Sasha Levin <[email protected]>:

Quoted 6 lines

Hi all,

While fuzzing with trinity inside a KVM tools guest running the latest -next kernel, I've stumbled on the following spew:

[ 2015.960381] general protection fault: 0000 [#1] PREEMPT SMP KASAN

Actually this is NULL-ptr dereference. Since you are using kasan with inline instrumentation
NULL-ptr deref transforms into GPF.

Quoted 5 lines
[ 2015.970534] RAX: 0000000000000000 RBX: ffff88000003a960 RCX: 0000000000000073
[ 2015.970534] RDX: 1ffff10101c8f3c4 RSI: 0000000000000000 RDI: ffff88080e479e20
[ 2015.970534] RBP: ffff88080e477a28 R08: 0000000000000066 R09: 0000000000000073
[ 2015.970534] R10: ffffda0017d55630 R11: dfffe90000000000 R12: ffff88005fc644b8
[ 2015.970534] R13: dfffe90000000000 R14: ffffffff92464884 R15: 0000000000000000

[...]

Quoted 13 lines

All code
========

   0:   e8 03 42 80 3c          callq  0x3c804208
   5:   28 00                   sub    %al,(%rax)
   7:   0f 85 ff 01 00 00       jne    0x20c
   d:   4c 8b 7b 18             mov    0x18(%rbx),%r15
  11:   4d 85 ff                test   %r15,%r15
  14:   0f 84 de 01 00 00       je     0x1f8
  1a:   41 f6 c7 07             test   $0x7,%r15b
  1e:   0f 85 d4 01 00 00       jne    0x1f8
  24:   4c 89 f8                mov    %r15,%rax
  27:   48 c1 e8 03             shr    $0x3,%rax
  2b:*  42 80 3c 28 00          cmpb   $0x0,(%rax,%r13,1)               <-- trapping instruction

Three commands above are result of KASAN's instrumentation. They check shadow for address in %r15:

     if (*((%r15 >> 3) + kasan_shadow_offset)
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
  30:   0f 85 b5 01 00 00       jne    0x1eb
  36:   4d 8b 37                mov    (%r15),%r14

And here is memory access, that KASAN checking.

Then frankly I suspect this is a KASAN bug.

Sure it is possible, but I don't see any evidence of kasan bug here.

Quoted 6 lines

These two instructions:

Quoted 2 lines
Quoted 2 lines
  11:   4d 85 ff                test   %r15,%r15
  14:   0f 84 de 01 00 00       je     0x1f8

Should prevent a NULL %r15 value from ever reaching the trapping instruction.

If they were executed, then yes. But I think there was jump from somewhere to the instructions below those two.

Quoted 3 lines

What other horrible things does KASAN do to the machine code?

kasan insert something like following before any memory access:

s8 *shadow_addr = (add >> 3) + shadow_offset;

if (unlikely(*shadow_addr))

     if (unlikely(addr & 7 >= *shadow_addr))
           report_bug(addr);

I suspect that Sasha is using kasan along with ubsan. In that case generated code much more horrid.

#4 lore raw
Quoted 10 lines · Andrey Ryabinin

2014-12-22 18:51 GMT+03:00 Eric W. Biederman <[email protected]>:

Quoted 6 lines

These two instructions:

Quoted 2 lines
Quoted 2 lines
  11:   4d 85 ff                test   %r15,%r15
  14:   0f 84 de 01 00 00       je     0x1f8

Should prevent a NULL %r15 value from ever reaching the trapping instruction.

If they were executed, then yes. But I think there was jump from somewhere to the instructions below those two.

There is indeed a jump direct to that point, which avoids the %r15 check.

Quoted 7 lines
Quoted 2 lines

What other horrible things does KASAN do to the machine code?

kasan insert something like following before any memory access:

s8 *shadow_addr = (add >> 3) + shadow_offset;

Quoted 7 lines

if (unlikely(*shadow_addr))

     if (unlikely(addr & 7 >= *shadow_addr))
           report_bug(addr);

I suspect that Sasha is using kasan along with ubsan. In that case generated code much more horrid.

It's not *that* bad :)

Thanks,
Sasha

#5 lore raw
Quoted 6 lines · Sasha Levin
Quoted 5 lines · Andrey Ryabinin

2014-12-22 18:51 GMT+03:00 Eric W. Biederman <[email protected]>:

Quoted 4 lines

These two instructions:

Quoted 2 lines
Quoted 2 lines
  11:   4d 85 ff                test   %r15,%r15
  14:   0f 84 de 01 00 00       je     0x1f8
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

Should prevent a NULL %r15 value from ever reaching the trapping instruction.

If they were executed, then yes. But I think there was jump from somewhere to the instructions below those two.

There is indeed a jump direct to that point, which avoids the %r15 check.

Where do you see that direct jump, that certainly has not been posted in this thread?

There are certainly no such code paths I in the source code. There is only one NULL pointer check in find_entry and it is executed every time the loop executes.

So at this point all I know is some set of tools has totally destroyed the code and made what Sasha Levin's is testing so far from the source code that this is a useless bug report.

I have no reason to even suspect this bug is actually in the upstream kernel.

This appears to be a kind of testing that slows development and wastes peoples time. Can someone give me a patch that sets the TAINTED flag when KASAN is loaded?

Eric

#6 lore raw

2014-12-22 23:39 GMT+03:00 Eric W. Biederman <[email protected]>:

Quoted 24 lines
Quoted 6 lines · Sasha Levin
Quoted 5 lines · Andrey Ryabinin

2014-12-22 18:51 GMT+03:00 Eric W. Biederman <[email protected]>:

Quoted 4 lines

These two instructions:

Quoted 2 lines
Quoted 2 lines
  11:   4d 85 ff                test   %r15,%r15
  14:   0f 84 de 01 00 00       je     0x1f8
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

Should prevent a NULL %r15 value from ever reaching the trapping instruction.

If they were executed, then yes. But I think there was jump from somewhere to the instructions below those two.

There is indeed a jump direct to that point, which avoids the %r15 check.

Where do you see that direct jump, that certainly has not been posted in this thread?

There are certainly no such code paths I in the source code. There is only one NULL pointer check in find_entry and it is executed every time the loop executes.

Quoted 7 lines

So at this point all I know is some set of tools has totally destroyed the code and made what Sasha Levin's is testing so far from the source code that this is a useless bug report.

I have no reason to even suspect this bug is actually in the upstream kernel.

Generated code looks correct to me (considering that it was built with sanitizer tools).
So this looks like a real BUG to me.

AFAICT this is 'head' == NULL:

   head = ctl_node->header;
   entry = &head->ctl_table[ctl_node - head->node];
Quoted 4 lines

This appears to be a kind of testing that slows development and wastes peoples time. Can someone give me a patch that sets the TAINTED flag when KASAN is loaded?

Pay attention to the first line of report:

[ 2015.960381] general protection fault: 0000 [#1] PREEMPT SMP KASAN
#7 lore raw
In reply to Sasha Levin
Quoted 4 lines · Sasha Levin

Hi all,

While fuzzing with trinity inside a KVM tools guest running the latest -next kernel, I've stumbled on the following spew:

Weird.

Quoted 1 line

2b:* 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1) <-- trapping instruction

%rax == 0
%r13 == dfffe90000000000
%r15 == 0 (%rax is derived from this)

That value of %r13 looks like an stomped pointer.

According to the disassembly %r15 is tested for 0 shortly before we get to the faulting instruction. So we should never have reached the faulting instruction in the first place.

The byte instructions from the disassembly are weird, but may make sense if strlen or and memcmp from namecmp were inlined. Although if that is what I am reading your line numbers are wrong stack backtrace.

I suspect the data structure got stomped somewhere.

If the stack trace didn't look sensible I would suspect someone jumped into the middle of find_entry from somewhere else.

In there any chance you could take your vmlinux and use objdump to dump the entire assembly of find_entry (that proc_sys_lookup calls?). I am suspecting the code you have and the code that is supposed to be there don't match.

Short of seeing something when comparing the disassembly of find_entry with the crash time text of find_entry I don't see any path to pursue. None of the pieces seem to add up.

Eric

Quoted 85 lines
[ 2015.960381] general protection fault: 0000 [#1] PREEMPT SMP KASAN
[ 2015.961912] Dumping ftrace buffer:
[ 2015.962803]    (ftrace buffer empty)
[ 2015.963370] Modules linked in:
[ 2015.963895] CPU: 1 PID: 16983 Comm: trinity-c126 Not tainted 3.18.0-next-20141219-sasha-00047-gaab33f6-dirty #1627
[ 2015.965991] task: ffff88080e478000 ti: ffff88080e474000 task.ti: ffff88080e474000
[ 2015.968196] RIP: find_entry (fs/proc/proc_sysctl.c:95)
[ 2015.970534] RSP: 0018:ffff88080e4779d8  EFLAGS: 00010246
[ 2015.970534] RAX: 0000000000000000 RBX: ffff88000003a960 RCX: 0000000000000073
[ 2015.970534] RDX: 1ffff10101c8f3c4 RSI: 0000000000000000 RDI: ffff88080e479e20
[ 2015.970534] RBP: ffff88080e477a28 R08: 0000000000000066 R09: 0000000000000073
[ 2015.970534] R10: ffffda0017d55630 R11: dfffe90000000000 R12: ffff88005fc644b8
[ 2015.970534] R13: dfffe90000000000 R14: ffffffff92464884 R15: 0000000000000000
[ 2015.970534] FS:  00007f9cd6c6f700(0000) GS:ffff8800c2200000(0000) knlGS:0000000000000000
[ 2015.970534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2015.970534] CR2: 00007f9cd0b9c000 CR3: 00000008193fb000 CR4: 00000000000006a0
[ 2015.970534] DR0: ffffffffff000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 2015.970534] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
[ 2015.970534] Stack:
[ 2015.970534]  ffff88080e477a28 ffff88080e477a50 00000003beaab0c0 ffff8800beaab0f8
[ 2015.970534]  0000000000000001 ffff8800beaab0f8 ffff8800beaab0c0 ffff8806079af638
[ 2015.970534]  0000000000000003 ffff88045f3cc000 ffff88080e477a88 ffffffff81c4e0ef
[ 2015.970534] Call Trace:
[ 2015.970534] proc_sys_lookup (fs/proc/proc_sysctl.c:303 fs/proc/proc_sysctl.c:452)
[ 2015.970534] ? d_alloc (fs/dcache.c:1499)
[ 2015.970534] lookup_real (fs/namei.c:1371)
[ 2015.970534] __lookup_hash (fs/namei.c:1390)
[ 2015.970534] link_path_walk (fs/namei.c:1496 fs/namei.c:1576 fs/namei.c:1830)
[ 2015.970534] ? preempt_count_sub (kernel/sched/core.c:2620)
[ 2015.970534] ? get_parent_ip (kernel/sched/core.c:2564)
[ 2015.970534] ? get_parent_ip (kernel/sched/core.c:2564)
[ 2015.970534] ? __cmpxchg_double_slab.isra.4 (./arch/x86/include/asm/preempt.h:95 include/linux/bit_spinlock.h:81 mm/slub.c:346 mm/slub.c:386)
[ 2015.970534] path_init (fs/namei.c:1947)
[ 2015.970534] ? deactivate_slab (include/linux/spinlock.h:349 mm/slub.c:1945)
[ 2015.970534] path_lookupat (fs/namei.c:1989)
[ 2015.970534] ? alloc_debug_processing (mm/slub.c:1044)
[ 2015.970534] filename_lookup (fs/namei.c:2025)
[ 2015.970534] kern_path_create (fs/namei.c:3309)
[ 2015.970534] ? getname_flags (fs/namei.c:159)
[ 2015.970534] ? vtime_account_user (kernel/sched/cputime.c:701)
[ 2015.970534] user_path_create (fs/namei.c:3381)
[ 2015.970534] SyS_mknod (fs/namei.c:3443 fs/namei.c:3431 fs/namei.c:3475 fs/namei.c:3473)
[ 2015.970534] tracesys_phase2 (arch/x86/kernel/entry_64.S:529)
[ 2015.970534] Code: e8 03 42 80 3c 28 00 0f 85 ff 01 00 00 4c 8b 7b 18 4d 85 ff 0f 84 de 01 00 00 41 f6 c7 07 0f 85 d4 01 00 00 4c 89 f8 48 c1 e8 03 <42> 80 3c 28 00 0f 85 b5 01 00 00 4d 8b 37 4d 85 ff 0f 84 55 02
All code
========
   0:	e8 03 42 80 3c       	callq  0x3c804208
   5:	28 00                	sub    %al,(%rax)
   7:	0f 85 ff 01 00 00    	jne    0x20c
   d:	4c 8b 7b 18          	mov    0x18(%rbx),%r15
  11:	4d 85 ff             	test   %r15,%r15
  14:	0f 84 de 01 00 00    	je     0x1f8
  1a:	41 f6 c7 07          	test   $0x7,%r15b
  1e:	0f 85 d4 01 00 00    	jne    0x1f8
  24:	4c 89 f8             	mov    %r15,%rax
  27:	48 c1 e8 03          	shr    $0x3,%rax
  2b:*	42 80 3c 28 00       	cmpb   $0x0,(%rax,%r13,1)		<-- trapping instruction
  30:	0f 85 b5 01 00 00    	jne    0x1eb
  36:	4d 8b 37             	mov    (%r15),%r14
  39:	4d 85 ff             	test   %r15,%r15
  3c:	0f                   	.byte 0xf
  3d:	84 55 02             	test   %dl,0x2(%rbp)
	...

Code starting with the faulting instruction
===========================================

   0:	42 80 3c 28 00       	cmpb   $0x0,(%rax,%r13,1)
   5:	0f 85 b5 01 00 00    	jne    0x1c0
   b:	4d 8b 37             	mov    (%r15),%r14
   e:	4d 85 ff             	test   %r15,%r15
  11:	0f                   	.byte 0xf
  12:	84 55 02             	test   %dl,0x2(%rbp)
	...
[ 2015.970534] RIP find_entry (fs/proc/proc_sysctl.c:95)
[ 2015.970534]  RSP <ffff88080e4779d8>
[ 2016.028073] ---[ end trace 142d37d0fb80aa87 ]---
[ 2016.028925] Kernel panic - not syncing: Fatal exception
[ 2016.030263] Dumping ftrace buffer:
[ 2016.030847]    (ftrace buffer empty)
[ 2016.031399] Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 2016.032890] Rebooting in 1 seconds..

Thanks,
Sasha