From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9235 Path: news.gmane.org!not-for-mail From: Josiah Worcester Newsgroups: gmane.linux.lib.musl.general Subject: Re: syscall_cp Date: Fri, 29 Jan 2016 22:50:47 +0000 Message-ID: References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113db7b44aa53d052a80de1f X-Trace: ger.gmane.org 1454107875 31764 80.91.229.3 (29 Jan 2016 22:51:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Jan 2016 22:51:15 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9248-gllmg-musl=m.gmane.org@lists.openwall.com Fri Jan 29 23:51:14 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 1aPHsl-00038b-A8 for gllmg-musl@m.gmane.org; Fri, 29 Jan 2016 23:51:11 +0100 Original-Received: (qmail 9768 invoked by uid 550); 29 Jan 2016 22:51:09 -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 9749 invoked from network); 29 Jan 2016 22:51:08 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=VbkHyt7VozAYi/VfG9FYKw1B74LpKgRncgGuGX/W3b0=; b=JL75cXH0WCLtFNZMDw9OVzsxPnMdDf3VgjpiNa/tS6/Lgu6eHsiKUw83nm66Nl1BmG yu1TJQgcY821iQ9+jZPjKch/Z5p9elR4ncBu6AtHFz1m1OW3Qdun+bM74D6d/IVIv04G 7PexC5uI9pwf6q9K9PQtu9uWQLDkXrAeyfQN4PZxWj04uUxSDdtNxUa/GSf3oMhvzm0N swbQuFjPcgQxzErCVmXp8l9BvI5Io/W9ofzlzQzxDPZ0E3Ak1jQv2lv8JvTZqthpay3I WSh1ONvHzzpLaghHHEE8YaXiiKI4OdYuT34fLXCtol9hYSZOpVVGhnBhpPc9CXhC/sfT zb0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=VbkHyt7VozAYi/VfG9FYKw1B74LpKgRncgGuGX/W3b0=; b=jIuggoPffxK8dO96VfcUrHVu86eqV4YwEjhCESAK50+oJSNnk1yesOSULP85Y1Nd6U WcORirKvSfYFS49txgN33mmLEmtjJ6Tz1/D2puJjk022y5rOgzf/19A3COOnLj/XiHoJ S3xVdI0Mld4APfZs7f7SmSsNhji6vsypxtt30xzEUHjCI2VHmjUxOsQ/QE6BZLlr7FwQ 7xyk+FWSHmqeMO7d0QcC/tu69BJE2wCWJU7MgXZOj4Om+aNOfbz7G3TFCc+tt9JO87oM 5qOyK6xEgrhi3rJaJ5srlgR1YkhWRwNtST6RjZwQb8F98jcSPZC1X3QU4BO/lnqrceRz vHQQ== X-Gm-Message-State: AG10YORFDl+F43LtWe6UMOr0U2jzMO1cN635silk1LZPGQY5nbxuhxOLGYbdLLs396dOBzHkJGrvVc/d0cPreg== X-Received: by 10.202.73.213 with SMTP id w204mr8682536oia.0.1454107857165; Fri, 29 Jan 2016 14:50:57 -0800 (PST) In-Reply-To: Xref: news.gmane.org gmane.linux.lib.musl.general:9235 Archived-At: --001a113db7b44aa53d052a80de1f Content-Type: text/plain; charset=UTF-8 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 > --001a113db7b44aa53d052a80de1f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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.)

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?<= /div>


--
Max Ruttenberg,
Member of = the Technical Staff
Em= u=C2=A0Technology
1400 E Angela Blvd, Unit 101
South Bend= , IN 46617
--001a113db7b44aa53d052a80de1f--