From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9236 Path: news.gmane.org!not-for-mail From: Max Ruttenberg Newsgroups: gmane.linux.lib.musl.general Subject: Re: syscall_cp Date: Fri, 29 Jan 2016 18:03:54 -0500 Message-ID: References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1136935ea469fc052a810c75 X-Trace: ger.gmane.org 1454108650 11362 80.91.229.3 (29 Jan 2016 23:04:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Jan 2016 23:04:10 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9249-gllmg-musl=m.gmane.org@lists.openwall.com Sat Jan 30 00:04:09 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1aPI5J-0001yk-10 for gllmg-musl@m.gmane.org; Sat, 30 Jan 2016 00:04:09 +0100 Original-Received: (qmail 15936 invoked by uid 550); 29 Jan 2016 23:04:07 -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 15908 invoked from network); 29 Jan 2016 23:04:06 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emutechnology-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=KkDGfvd52DWqU5LPFhsdgaPMo7z3yGJMPhlL1sRRIaQ=; b=LG0XwCGkEhyNiAPWAJwcl4x+FO0GW3nzJTmDLQMk1ypuiLrr0K3uSzNgs7xSVlRa8Y vQEwROwlTgNlq0NBHWkKMwLsHPlW6DOK7wfTt4jwiFPhmba+x4Wm8yOmKqFr2BzOFXEX 8MW8xmMWgTe2J/wYu0M/vWTPsP+ppIuAiRGTUk0vOUFqWIrzBc/i+xiOIxzSdagR4jo6 w3IWzce7wbvX8ZRzQWGubCL4NkzA9/mCIPY9/gx1WOMW9aIZojcIB56N8Y0om/L+Lf2D agX6QMq5Aryf/xKeJ31UorpNGa1sU5rKcE7cOd2h8fnldJYaYLTFnJ24N2tfgEB4fcjV F0lQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=KkDGfvd52DWqU5LPFhsdgaPMo7z3yGJMPhlL1sRRIaQ=; b=dQyZ3gM8YXO38YDEgA3UqyQPacP0Vo/8ffpN9vtPxHqSoC/yu8a1bTeVonagFfzwVh vft7iNiybfaDHagA8mHzwQETsR3olOW7iaKi5hCVqqO7cdFf00B1FhMqMqcw5OslQPoR 6AP9SV+BuDrhI29/C7blzSyviXfWJI98P+KJmVFjxNHmMD8qvLjP5Ig0B1ayUH76MmAM BsYmKKALBecqNz3dGpdbq6Dhy18RX2VnfsaFgnVyB5NZfd8AuoYhHnAYGlESULuLJbLA f1RIqENpm5ZAJ73ypYT2QjcmWtcd5pU72XECYU2FpyjT6g/saNts4KvOm9yftUJAZq5s IY5Q== X-Gm-Message-State: AG10YOSavU6IgIjqLZ+riJYesefPWRltqdxN/qrOdd1Tc8sU86mG42AsSX5MtYJEFWIddDebSU9mD5rC3e0oug== X-Received: by 10.60.227.74 with SMTP id ry10mr2858044oec.48.1454108634786; Fri, 29 Jan 2016 15:03:54 -0800 (PST) In-Reply-To: Xref: news.gmane.org gmane.linux.lib.musl.general:9236 Archived-At: --001a1136935ea469fc052a810c75 Content-Type: text/plain; charset=UTF-8 and syscall_ret ?? On Fri, Jan 29, 2016 at 5:50 PM, Josiah Worcester wrote: > syscall_cp does largely the same thing as syscall. However, it also checks > for a current cancellation request, and exports some symbols (before and > after the syscall call) which are used in the thread cancellation > implementation. It makes it so the cancellation handler can know whether or > not the cancellation request happened during or after a syscall. (if > during, it needs to cancel the thread, if after, then it needs to continue > executing until the next cancellation point.) > > On Fri, Jan 29, 2016 at 2:41 PM Max Ruttenberg < > mruttenberg@emutechnology.com> wrote: > >> What is syscall_cp and what is it supposed to do that syscall isn't? >> >> >> -- >> Max Ruttenberg, >> Member of the Technical Staff >> Emu *Technology* >> 1400 E Angela Blvd, Unit 101 >> South Bend, IN 46617 >> > -- Max Ruttenberg, Member of the Technical Staff Emu *Technology* 1400 E Angela Blvd, Unit 101 South Bend, IN 46617 --001a1136935ea469fc052a810c75 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
and syscall_ret ??

On Fri, Jan 29, 2016 at 5:50 PM, Josiah Worcester <= span dir=3D"ltr"><josiahw@gmail.com> wrote:
=
syscall_cp does largely the same thing as syscall. However= , it also checks for a current cancellation request, and exports some symbo= ls (before and after the syscall call) which are used in the thread cancell= ation implementation. It makes it so the cancellation handler can know whet= her or not the cancellation request happened during or after a syscall. (if= during, it needs to cancel the thread, if after, then it needs to continue= executing until the next cancellation point.)
<= div class=3D"h5">
On Fri, Ja= n 29, 2016 at 2:41 PM Max Ruttenberg <mruttenberg@emutechnology.com> wrot= e:
What is syscall= _cp and what is it supposed to do that syscall isn't?


--
Max Ruttenberg,
Member of the Technical Sta= ff
= Emu=C2=A0Technology
1400 E Angela Blvd, Unit 101
South Bend, IN 46617
<= /div>



--
=
Max Ruttenbe= rg,
Member of the Technical Staff
Emu=C2=A0Technology
1400 E Angela Blvd, Unit 101
South Bend, IN 46617
<= /div>
--001a1136935ea469fc052a810c75--