Comment 5 for bug 1634519

This is reproduceable on my QEMU instance:

13:16:59 DEBUG| [stdout] opcode PASSED
13:17:10 DEBUG| [stdout] open PASSED
13:17:20 DEBUG| [stdout] personality PASSED
13:17:30 DEBUG| [stdout] pipe PASSED
13:17:40 DEBUG| [stdout] poll PASSED

And we get:

[ 5361.167961] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ffffffff84f6b18e
[ 5361.167961]
[ 5361.171800] CPU: 1 PID: 19248 Comm: Tainted: G W OE 4.8.0-26-generic #28-Ubuntu
[ 5361.173179] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu2 04/01/2014
[ 5361.175119] 0000000000000086 0000000094818d37 ffff8b7b72acbc78 ffffffff8502f5b2
[ 5361.176740] 0000000094f6b400 ffffffff85883520 ffff8b7b72acbd00 ffffffff84d9e71c
[ 5361.178356] ffff8b7b00000010 ffff8b7b72acbd10 ffff8b7b72acbca8 0000000094818d37
[ 5361.179938] Call Trace:
[ 5361.180420] [<ffffffff8502f5b2>] dump_stack+0x63/0x81
[ 5361.181401] [<ffffffff84d9e71c>] panic+0xe4/0x226
[ 5361.182310] [<ffffffff84f6b18e>] ? proc_keys_show+0x3ce/0x3d0
[ 5361.183487] [<ffffffff84c82b89>] __stack_chk_fail+0x19/0x30
[ 5361.184478] [<ffffffff84f6b18e>] proc_keys_show+0x3ce/0x3d0
[ 5361.185476] [<ffffffff84f68690>] ? key_validate+0x50/0x50
[ 5361.187078] [<ffffffff84f65d50>] ? key_default_cmp+0x20/0x20
[ 5361.188277] [<ffffffff84e599f9>] seq_read+0x2e9/0x3c0
[ 5361.189303] [<ffffffff84ea62e2>] proc_reg_read+0x42/0x70
[ 5361.190234] [<ffffffff84e32428>] __vfs_read+0x18/0x40
[ 5361.190813] [<ffffffff84e32b86>] vfs_read+0x96/0x130
[ 5361.191732] [<ffffffff84e34065>] SyS_read+0x55/0xc0
[ 5361.192739] [<ffffffff8549f076>] entry_SYSCALL_64_fastpath+0x1e/0xa8
[ 5361.194353] Kernel Offset: 0x3c00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 5361.197761] ---[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ffffffff84f6b18e

This is because of bug 1634496.