When i run a vmware workstation windows 10 guest on an ext4 nvme drive, I get a kernel crash. The same guest seems stable on an ext4 filesystem on a spinning disk. Should i report this to kernel devs, and if so, how?
Dec 31 17:20:39 sysname kernel: ------------[ cut here ]------------ Dec 31 17:20:40 sysname kernel: WARNING: CPU: 5 PID: 4935 at fs/ext4/inode.c:3842 ext4_set_page_dirty+0x39/0x50 Dec 31 17:20:40 sysname kernel: Modules linked in: vmw_vsock_vmci_transport vmnet(O) vmw_vmci vmblock(O) vsock vmmon(O) cfg80211 rfkill auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd grace sunrpc hid_microsoft aesni_intel crypto_simd cryptd fam15h_power snd_hda_codec_hdmi glue_helper snd_hda_codec_realtek snd_hda_codec_generic alx k10temp mdio ohci_pci i2c_piix4 ohci_hcd snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core snd_pcm snd_timer sch_fq_codel Dec 31 17:20:40 sysname kernel: CPU: 5 PID: 4935 Comm: vmx-vcpu-2 Tainted: G O 4.14.9-gentoo #1 Dec 31 17:20:40 sysname kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./GA-990FX-GAMING, BIOS NV1 11/03/2015 Dec 31 17:20:40 sysname kernel: task: ffff9e8c014b0040 task.stack: ffffb65bc5540000 Dec 31 17:20:40 sysname kernel: RIP: 0010:ext4_set_page_dirty+0x39/0x50 Dec 31 17:20:40 sysname kernel: RSP: 0018:ffffb65bc5543d70 EFLAGS: 00010246 Dec 31 17:20:40 sysname kernel: RAX: 01ffe0000000102c RBX: ffff9e8d048db460 RCX: 0000000000000000 Dec 31 17:20:40 sysname kernel: RDX: 0000000000000000 RSI: 0000000000000041 RDI: ffffe5f0c6944440 Dec 31 17:20:40 sysname kernel: RBP: 0000000000000041 R08: ffffb65c00000000 R09: 00003ffffffff000 Dec 31 17:20:40 sysname kernel: R10: ffff9e8bfec42910 R11: ffff9e8c014b0040 R12: 0000000000000001 Dec 31 17:20:40 sysname kernel: R13: ffff9e8d048db460 R14: 0000000000000000 R15: 0000000000000002 Dec 31 17:20:40 sysname kernel: FS: 00007fe07b7f5700(0000) GS:ffff9e8d3ed40000(0000) knlGS:0000000000000000 Dec 31 17:20:40 sysname kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 31 17:20:40 sysname kernel: CR2: 00007fe0a31fd000 CR3: 00000003017a8000 CR4: 00000000000406e0 Dec 31 17:20:40 sysname kernel: Call Trace: Dec 31 17:20:40 sysname kernel: qp_release_pages+0x5b/0x70 [vmw_vmci] Dec 31 17:20:40 sysname kernel: qp_host_unregister_user_memory.isra.20+0x1d/0x70 [vmw_vmci] Dec 31 17:20:40 sysname kernel: vmci_qp_broker_detach+0x23d/0x3f0 [vmw_vmci] Dec 31 17:20:40 sysname kernel: vmci_host_unlocked_ioctl+0x1b7/0xb90 [vmw_vmci] Dec 31 17:20:40 sysname kernel: do_vfs_ioctl+0xa0/0x660 Dec 31 17:20:40 sysname kernel: ? vfs_read+0xe4/0x100 Dec 31 17:20:40 sysname kernel: SyS_ioctl+0x6f/0x80 Dec 31 17:20:40 sysname kernel: entry_SYSCALL_64_fastpath+0x13/0x6c Dec 31 17:20:40 sysname kernel: RIP: 0033:0x7fe1af175ea7 Dec 31 17:20:40 sysname kernel: RSP: 002b:00007fe07b7ecad8 EFLAGS: 00003246 ORIG_RAX: 0000000000000010 Dec 31 17:20:40 sysname kernel: RAX: ffffffffffffffda RBX: 0000564d1d4030b0 RCX: 00007fe1af175ea7 Dec 31 17:20:40 sysname kernel: RDX: 00007fe07b7ecaf0 RSI: 00000000000007aa RDI: 00000000000000cb Dec 31 17:20:40 sysname kernel: RBP: 0000000000000175 R08: 0000000000000002 R09: 00007fe07b7ecc80 Dec 31 17:20:40 sysname kernel: R10: 0000000000000000 R11: 0000000000003246 R12: 0000564d1d3fb8e8 Dec 31 17:20:40 sysname kernel: R13: 0000564d1d403809 R14: 0000000000000002 R15: 0000000000000050 Dec 31 17:20:40 sysname kernel: Code: c7 48 8b 00 a8 01 75 16 48 8b 57 20 48 8d 42 ff 83 e2 01 48 0f 44 c7 48 8b 00 a8 10 74 0d 48 8b 07 f6 c4 10 74 0f e9 a7 ce f9 ff <0f> ff 48 8b 07 f6 c4 10 75 f1 0f ff e9 96 ce f9 ff 66 0f 1f 44 Dec 31 17:20:40 sysname kernel: ---[ end trace bdcc9ef5a4c4713c ]---
