System crash with 'general protection fault: 0000 [#1] SMP' and BUG kmalloc-256

Issue

• System crash with general protection fault: 0000 [#1] SMP. Kernel log buffer shows BUG kmalloc-256 errors as well:

[  485.782961] =============================================================================
[  485.792109] BUG kmalloc-256(1:1f668e7b2418a525691961a9bd0d4b0c65ccc4a64c144825b5f6d3bb332dbc14) (Tainted: G    B      OE  ------------ T): Objects remaining in kmalloc-256(1:1f668e7b2418a525691961a9bd0d4b0c65ccc4a64c144825b5f6d3bb332dbc14
[  485.815726] -----------------------------------------------------------------------------
[...]
[  486.185464] general protection fault: 0000 [#1] SMP 
[...]
[  486.271154]  fjes dca crc32c_intel usb_storage [last unloaded: gpio_ich]
[  486.277211] CPU: 4 PID: 10528 Comm: lvremove Tainted: G    B      OE  ------------ T 3.10.0-514.6.1.el7.x86_64 #1
[  486.288679] Hardware name: TOSHIBA OX/OX, BIOS OX-T002 03/02/2017
[  486.295487] task: ffff8803e3653ec0 ti: ffff8803f5fb4000 task.ti: ffff8803f5fb4000
[  486.303847] RIP: 0010:[<ffffffff811df911>]  [<ffffffff811df911>] kmem_cache_close+0xc1/0x2f0
[  486.313277] RSP: 0018:ffff8803f5fb7b90  EFLAGS: 00010202
[  486.319209] RAX: ffff88046aff4301 RBX: ffff8803eba44000 RCX: 0000000000008a94
[  486.327179] RDX: 0000000000008a93 RSI: 0000000000001f00 RDI: ffff880187c03e00
[  486.335150] RBP: ffff8803f5fb7be0 R08: 0000000000019a20 R09: ffffffff811dfa35
[  486.343121] R10: ffff88047fd19a20 R11: ffffea0011abfd00 R12: ffffea000fae9080
[  486.351092] R13: ffff8803eba42000 R14: ffff88046f4acf00 R15: dead0000000000e0
[  486.359065] FS:  00007f33efb8a880(0000) GS:ffff88047fd00000(0000) knlGS:0000000000000000
[  486.368104] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  486.374521] CR2: 00007f4d87886000 CR3: 00000003d43e3000 CR4: 00000000001007e0
[  486.382491] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  486.390462] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  486.398422] Stack:
[  486.400661]  ffff88046f4acf00 0000000087c03700 ffff88046ba393c0 ffff88046aff4398
[  486.408940]  ffff88046ba393d0 ffff88046f4acf00 ffff88046f4acf00 ffff880187c03700
[  486.417220]  ffff88046cf53600 0000000000000131 ffff8803f5fb7c00 ffffffff811dfb54
[  486.425499] Call Trace:
[  486.428229]  [<ffffffff811dfb54>] __kmem_cache_shutdown+0x14/0x80
[  486.435037]  [<ffffffff811a5854>] kmem_cache_destroy+0x44/0xf0
[  486.441552]  [<ffffffff811f3e99>] kmem_cache_destroy_memcg_children+0x89/0xb0
[  486.449524]  [<ffffffff811a5829>] kmem_cache_destroy+0x19/0xf0
[  486.456038]  [<ffffffff8123756e>] bioset_free+0xce/0x110
[  486.461982]  [<ffffffffa02329de>] __dm_destroy+0x19e/0x320 [dm_mod]
[  486.468987]  [<ffffffffa0233833>] dm_destroy+0x13/0x20 [dm_mod]
[  486.475604]  [<ffffffffa02393de>] dev_remove+0x11e/0x180 [dm_mod]
[  486.482414]  [<ffffffffa02392c0>] ? dev_suspend+0x250/0x250 [dm_mod]
[  486.489516]  [<ffffffffa0239a35>] ctl_ioctl+0x1e5/0x500 [dm_mod]
[  486.496238]  [<ffffffffa0239d63>] dm_ctl_ioctl+0x13/0x20 [dm_mod]
[  486.503049]  [<ffffffff81212025>] do_vfs_ioctl+0x2d5/0x4b0
[  486.509180]  [<ffffffff812aebae>] ? file_has_perm+0xae/0xc0
[  486.515408]  [<ffffffff812122a1>] SyS_ioctl+0xa1/0xc0
[  486.521055]  [<ffffffff816967c9>] system_call_fastpath+0x16/0x1b
[...]
[  486.549205] RIP  [<ffffffff811df911>] kmem_cache_close+0xc1/0x2f0
[  486.556020]  RSP <ffff8803f5fb7b90>

This issue has been seen twice at the time of this writing. In both cases, a LVM command triggered the panic and the systems were running Docker with the overlay module loaded.