From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14122 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "zhaohang (F)" Newsgroups: gmane.linux.lib.musl.general Subject: src/thread/__timedwait.c: Clock type Date: Mon, 13 May 2019 01:36:15 +0000 Message-ID: <59FB1E003EF3A943BD6BAD197ABD4D6A272CE7@dggemi524-mbx.china.huawei.com> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="_000_59FB1E003EF3A943BD6BAD197ABD4D6A272CE7dggemi524mbxchina_" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="65277"; mail-complaints-to="usenet@blaine.gmane.org" To: "musl@lists.openwall.com" Original-X-From: musl-return-14138-gllmg-musl=m.gmane.org@lists.openwall.com Mon May 13 03:36:37 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1hPztM-000Gpa-HU for gllmg-musl@m.gmane.org; Mon, 13 May 2019 03:36:36 +0200 Original-Received: (qmail 3926 invoked by uid 550); 13 May 2019 01:36:33 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 3889 invoked from network); 13 May 2019 01:36:32 -0000 Thread-Topic: src/thread/__timedwait.c: Clock type Thread-Index: AdUJKx4qsZxAH9JsTq2kcHRkXxueUg== Accept-Language: en-US Content-Language: zh-CN x-originating-ip: [10.177.224.64] X-CFilter-Loop: Reflected Xref: news.gmane.org gmane.linux.lib.musl.general:14122 Archived-At: --_000_59FB1E003EF3A943BD6BAD197ABD4D6A272CE7dggemi524mbxchina_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable In the function _timedwait_cp, 'clk' indicates the type of clock used, CLOC= K_REALTIME or CLOCK_MONOTONIC. when we call __syscall_cp in this function, the fifth parameter 'top' is ca= lculated based on the clock type. However, the third parameter is not set according to the clock type. CLOCK_= MONOTONIC is used by default. Is this a bug? Or other considerations? Thanks, Zhao Hang --_000_59FB1E003EF3A943BD6BAD197ABD4D6A272CE7dggemi524mbxchina_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

In the function _timedwait_cp, ‘clk’ indicates the type of clock used, CLOCK_REALTIME o= r CLOCK_MONOTONIC.

 

when we call __syscall_cp in th= is function, the fifth parameter ‘top’ is calculated based on t= he clock type.

 

However, the third parameter is= not set according to the clock type. CLOCK_MONOTONIC is used by default.

 

Is this a bug? Or other conside= rations?

 

Thanks,

 

Zhao Hang

--_000_59FB1E003EF3A943BD6BAD197ABD4D6A272CE7dggemi524mbxchina_--