From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9237 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: syscall_cp Date: Fri, 29 Jan 2016 18:16:04 -0500 Message-ID: <20160129231603.GB9349@brightrain.aerifal.cx> References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1454109394 22488 80.91.229.3 (29 Jan 2016 23:16:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Jan 2016 23:16:34 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9250-gllmg-musl=m.gmane.org@lists.openwall.com Sat Jan 30 00:16:20 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 1aPIH4-0008Tx-FN for gllmg-musl@m.gmane.org; Sat, 30 Jan 2016 00:16:18 +0100 Original-Received: (qmail 22459 invoked by uid 550); 29 Jan 2016 23:16:16 -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 22438 invoked from network); 29 Jan 2016 23:16:16 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:9237 Archived-At: On Fri, Jan 29, 2016 at 06:03:54PM -0500, Max Ruttenberg wrote: > and syscall_ret ?? It's a shortcut to avoid duplicating the errno update code in every syscall wrapper. Instead they all just tail call to __syscall_ret which returns -1 and sets errno if the return value was an error code, and otherwise just passes through the return value. BTW could you please reply inline-with/below quoted text on the list rather than top-posting? Top-posting makes it hard to follow the flow of conversation. Rich > 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