From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.seebs.net (mail.seebs.net [162.213.38.76]) by mail.openembedded.org (Postfix) with ESMTP id 7F41378836 for ; Fri, 23 Mar 2018 16:28:21 +0000 (UTC) Received: from seebsdell (unknown [24.196.59.174]) by mail.seebs.net (Postfix) with ESMTPSA id F19652E8928; Fri, 23 Mar 2018 11:28:21 -0500 (CDT) Date: Fri, 23 Mar 2018 11:28:20 -0500 From: Seebs To: Enrico Scholz Message-ID: <20180323112820.12bc94a4@seebsdell> In-Reply-To: References: X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Cc: OE-core Subject: Re: pseudo: host user contamination X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 16:28:21 -0000 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 23 Mar 2018 17:10:35 +0100 Enrico Scholz wrote: > I think, 'mv' is the culprit. It calls 'renameat2()' directly over > 'syscall()': > > | $ ltrace mv foo bar > | ... > | syscall(316, 0xffffff9c, 0x7fff1564a341, > 0xffffff9c) = 0 > > > Perhaps, 'pseudo' does not catch this? Yeah. And so far as I know, it's not actually *possible* to in the general case. I really don't think it's safe to try to catch syscall(). I was afraid someone would do this. (It also breaks most Go programs, for similar reasons; no libc calls.) I have no idea why they're doing that; it seems distinctly unsafe. -s