Re: Unkillable R-state process stuck in sendfile

2014-02-18 Thread Vladimir Davydov
On 02/18/2014 11:13 PM, valdis.kletni...@vt.edu wrote: > On Mon, 17 Feb 2014 16:51:37 +0400, Vladimir Davydov said: > >> out_fd = eventfd(0, 0); >> if (out_fd < 0) >> err(1, "eventfd"); >> ret = sendfile64(out_fd, in_fd, NULL, SIZE); >> I'm not sure if this

Re: Unkillable R-state process stuck in sendfile

2014-02-18 Thread Valdis . Kletnieks
On Mon, 17 Feb 2014 16:51:37 +0400, Vladimir Davydov said: > out_fd = eventfd(0, 0); > if (out_fd < 0) > err(1, "eventfd"); > ret = sendfile64(out_fd, in_fd, NULL, SIZE); > I'm not sure if this is actually bad and should be fixed, but perhaps > it's worth

Re: Unkillable R-state process stuck in sendfile

2014-02-18 Thread Valdis . Kletnieks
On Mon, 17 Feb 2014 16:51:37 +0400, Vladimir Davydov said: out_fd = eventfd(0, 0); if (out_fd 0) err(1, eventfd); ret = sendfile64(out_fd, in_fd, NULL, SIZE); I'm not sure if this is actually bad and should be fixed, but perhaps it's worth making

Re: Unkillable R-state process stuck in sendfile

2014-02-18 Thread Vladimir Davydov
On 02/18/2014 11:13 PM, valdis.kletni...@vt.edu wrote: On Mon, 17 Feb 2014 16:51:37 +0400, Vladimir Davydov said: out_fd = eventfd(0, 0); if (out_fd 0) err(1, eventfd); ret = sendfile64(out_fd, in_fd, NULL, SIZE); I'm not sure if this is actually bad

Unkillable R-state process stuck in sendfile

2014-02-17 Thread Vladimir Davydov
Hi, While running trinity syscall fuzzer I noticed that sometimes it does not get killed immediately, even by SIGKILL - it takes several minutes before it exits. What is interesting it "hangs" in R-state consuming 100% of CPU time. Analyzing its trace I found that it loops in sendfile(2) with the

Unkillable R-state process stuck in sendfile

2014-02-17 Thread Vladimir Davydov
Hi, While running trinity syscall fuzzer I noticed that sometimes it does not get killed immediately, even by SIGKILL - it takes several minutes before it exits. What is interesting it hangs in R-state consuming 100% of CPU time. Analyzing its trace I found that it loops in sendfile(2) with the