* [Question] How to deal D state on request_wait_answer?
@ 2020-11-17 9:01 Haotian Li
0 siblings, 0 replies; only message in thread
From: Haotian Li @ 2020-11-17 9:01 UTC (permalink / raw)
To: miklos, mszeredi, virtio-fs
Cc: linux-fsdevel, linux-kernel, liuzhiqiang (I), linfeilong, lixiaokeng
Hi
We recently detected a bug in virtiofs. Here, we created a
virtual machine as guest with Qemu and virtiofsd. We mounted
virtiofs on guest, for example /home/virtiofs. Then we killed
the virtiofsd in host and accessed /home/virtiofs in guest later.
This casued a process with D state which could not be killed.
The stack of the process as following:
wait_event_interruptible
[<0>] request_wait_answer+0x9d/0x210 [fuse]
[<0>] __fuse_request_send+0x75/0x80 [fuse]
[<0>] fuse_simple_request+0x164/0x270 [fuse]
[<0>] fuse_do_getattr+0xd5/0x2a0 [fuse]
[<0>] vfs_statx+0x89/0xe0
[<0>] __do_sys_newstat+0x39/0x70
[<0>] do_syscall_64+0x55/0x1c0
[<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
We have no idea to deal with the bug. Here, we have some
question about that:
1. Why not use timeout mechanism?
2. If timeout mechanism is used, the process will enter
wait_event after wait_event_interruptible_timeout?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-11-17 9:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-17 9:01 [Question] How to deal D state on request_wait_answer? Haotian Li
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).