From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/12737 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Possible issue around utime() and symlinks on at least MIPS64 Date: Wed, 18 Apr 2018 18:37:13 -0400 Message-ID: <20180418223713.GK3094@brightrain.aerifal.cx> References: <1628901.R1SNWt7Sda@zaphod> <20180418200014.GG3094@brightrain.aerifal.cx> <89968ffc-d4ae-93d1-0810-345ad03f2a53@adelielinux.org> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1524090922 30845 195.159.176.226 (18 Apr 2018 22:35:22 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 18 Apr 2018 22:35:22 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-12753-gllmg-musl=m.gmane.org@lists.openwall.com Thu Apr 19 00:35:18 2018 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.84_2) (envelope-from ) id 1f8vfZ-0007x9-OT for gllmg-musl@m.gmane.org; Thu, 19 Apr 2018 00:35:17 +0200 Original-Received: (qmail 17880 invoked by uid 550); 18 Apr 2018 22:37:26 -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 17862 invoked from network); 18 Apr 2018 22:37:25 -0000 Content-Disposition: inline In-Reply-To: <89968ffc-d4ae-93d1-0810-345ad03f2a53@adelielinux.org> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:12737 Archived-At: On Wed, Apr 18, 2018 at 04:51:31PM -0500, A. Wilcox wrote: > On 04/18/18 15:00, Rich Felker wrote: > > On Thu, Jul 06, 2017 at 02:50:16PM +0100, Adam Hill wrote: > >> Hi, > >> > >> Not carried out ANY investigation around this... unfortunately I > >> don't have any time atm. Could also have been mentioned already or > >> actually be a bug in tar itself etc. but I couldn't find anything > >> with my quick search. Just thought I'd mention it in case anyone > >> does feel inclined to investigate. > >> > >> I compiled OpenWrt using pretty much default build settings for an > >> octeon chip... it uses musl-1.1.16. The only real change I made was > >> to use GNU tar rather than busybox. The resulting tar binary can't > >> fix the modification/access times on any extracted symbolic links, > >> resulting in for example: > >> > >> tar: usr/share/zoneinfo/Africa: Cannot utime: Invalid argument > >> > >> I didn't have strace available so can't even be sure tar's using > >> utime()... just going by the error message alone. > >> > >> I recompiled OpenWrt changing only the C library ( to GCC ) and the > >> resulting tar binary worked fine... so I can only *assume* it's > >> something to do with musl. > > > > Did anyone ever get a chance to look further into this? It's been on > > my todo for a long time, but without sufficient information to > > reproduce I don't know where to begin. I spent about 20 minutes > > looking at the musl and kernel code now and it does not seem likely > > that this is mips64-specific. > > > > Rich > > > > This really sounds like broken cross-compiling. When we cross-compile > cp, it's unable to handle xattrs until it's re-compiled on native > hardware. I'd suggest poking around at autoconf for GNU tar and seeing > what it is 'guessing' the environment is like, and perhaps overriding > some with ac_*={yes,no} on the configure line. That's a good thought and would probably explain why we haven't hit a similar issue elsewhere. It probably also indicates a bug in gnulib/tar rather than musl. Rich