Displaying 2 results from an estimated 2 matches for "coredump_wait".
2005 Jan 14
1
xen-unstable dom0/1 smp schedule while atomic
...[evtchn_do_upcall+190/320] evtchn_do_upcall+0xbe/0x140
[work_resched+5/47] work_resched+0x5/0x2f
<snip>
scheduling while atomic
[schedule+1682/1696] schedule+0x692/0x6a0
[__change_page_attr+203/624] __change_page_attr+0xcb/0x270
[sys_sched_yield+89/112] sys_sched_yield+0x59/0x70
[coredump_wait+63/176] coredump_wait+0x3f/0xb0
[do_coredump+222/471] do_coredump+0xde/0x1d7
[__dequeue_signal+296/432] __dequeue_signal+0x128/0x1b0
[__dequeue_signal+245/432] __dequeue_signal+0xf5/0x1b0
[dequeue_signal+53/160] dequeue_signal+0x35/0xa0
[get_signal_to_deliver+599/848] get_signal_to_delive...
2023 May 24
1
[PATCH 3/3] fork, vhost: Use CLONE_THREAD to fix freezer/ps regression
On 05/23, Eric W. Biederman wrote:
>
> I want to point out that we need to consider not just SIGKILL, but
> SIGABRT that causes a coredump, as well as the process peforming
> an ordinary exit(2). All of which will cause get_signal to return
> SIGKILL in this context.
Yes, but probably SIGABRT/exit doesn't really differ from SIGKILL wrt
vhost_worker().
> It is probably not