Date: Sun, 21 Mar 2021 07:06:32 +0000 From: bugzilla-noreply@freebsd.org To: emulation@FreeBSD.org Subject: [Bug 252820] Linuxulator: linux_timerfd_settime don't set expirations count to zero Message-ID: <bug-252820-4077-hXXZMKsJcx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252820-4077@https.bugs.freebsd.org/bugzilla/> References: <bug-252820-4077@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252820 --- Comment #3 from commit-hook@FreeBSD.org --- A commit in branch stable/12 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3Dbf1863de6b1fb813192e45639b4cfde65= a624b6b commit bf1863de6b1fb813192e45639b4cfde65a624b6b Author: shu <ankohuu@outlook.com> AuthorDate: 2021-02-03 16:51:45 +0000 Commit: Dmitry Chagin <dchagin@FreeBSD.org> CommitDate: 2021-03-21 07:03:22 +0000 linux: make timerfd_settime(2) set expirations count to zero On Linux, read(2) from a timerfd file descriptor returns an unsigned 8-byte integer (uint64_t) containing the number of expirations that have occurred, if the timer has already expired one or more times since its settings were last modified using timerfd_settime(), or since the last successful read(2). That's to say, once we do a read or call timerfd_settime(), timer fd's expiration count should be zero. Some Linux applications create timerfd and add it to epoll with LT mode, when event comes, they do timerfd_settime instead of read to stop event source from trigger. On FreeBSD, timerfd_settime(2) didn't set the count to zero, which caused high CPU utilization. PR: 252820 Submitted by: ankohuu_outlook.com (Shunchao Hu) Differential Revision: https://reviews.freebsd.org/D28231 (cherry picked from commit ae71b794cbed19e5e25effc3438720ad452ab87c) sys/compat/linux/linux_event.c | 1 + 1 file changed, 1 insertion(+) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252820-4077-hXXZMKsJcx>