musl - Possible issue around utime() and symlinks on at least MIPS64

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1628901.R1SNWt7Sda@zaphod>
Date: Thu, 06 Jul 2017 14:50:16 +0100
From: Adam Hill <sidepipeuk@...il.com>
To: musl@...ts.openwall.com
Subject: Possible issue around utime() and symlinks on at least MIPS64

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.

Content of type "text/html" skipped

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.