[elbe-devel] Fwd: [elbe-users] elbe get_archive broken?

ew.foe at nassur.net ew.foe at nassur.net
Sun Nov 22 09:26:17 CET 2020


Forwarding to elbe-devel
Erich

----- Forwarded message from ew.foe at nassur.net -----
    Date: Mon, 16 Nov 2020 14:15:03 +0100
    From: ew.foe at nassur.net
Subject: [elbe-users] elbe get_archive broken?
      To: elbe-users at linutronix.de

Hello,

I upgraded to elbe-13.1. Everything seems to be python3 now, congrats!

I found a /regression/:

mkdir -p tmp/elbe-13
cd tmp/elbe-13
/space/ew/tools/elbe/v13.1/elbe --version
elbe v13.1

cp /space/ew/tools/elbe/v13.1/examples/armhf-ti-beaglebone-black.xml .
cp armhf-ti-beaglebone-black.xml tmp.armhf-ti-beaglebone-black.xml

mkdir -p local-changes/etc
date > local-changes/etc/zz.killroy.was.here
/space/ew/tools/elbe/v13.1/elbe chg_archive  
tmp.armhf-ti-beaglebone-black.xml ./local-changes/

Everything works up to this point. So now I want to retrieve the archive:

/space/ew/tools/elbe/v13.1/elbe get_archive  
tmp.armhf-ti-beaglebone-black.xml local.tar.bz2
Error writing archive

This works with elbe 12.5

A little inspection with strace hints at this call:
> 7604  13:23:27.672201 openat(AT_FDCWD, "local.tar.bz2",  
> O_WRONLY|O_CREAT|O_TRUNC, 0666) = 3
ok.
? 7579  13:21:37.726785 openat(AT_FDCWD, "local.tar.bz2",  
O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0666) = 3
fail

so this particular call to openat in 13.1 has one more flag set: O_CLOEXEC

> 7579  13:21:37.726785 openat(AT_FDCWD, "local.tar.bz2",  
> O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0666) = 3
> 7579  13:21:37.726923 fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> 7579  13:21:37.727040 ioctl(3, TCGETS, 0x7fff59d156b0) = -1 ENOTTY  
> (Inappropriate ioctl for device)
> 7579  13:21:37.727160 lseek(3, 0, SEEK_CUR) = 0
> 7579  13:21:37.727277 ioctl(3, TCGETS, 0x7fff59d155f0) = -1 ENOTTY  
> (Inappropriate ioctl for device)
> 7579  13:21:37.727405 lseek(3, 0, SEEK_CUR) = 0
> 7579  13:21:37.727548 write(1, "Error writing archive\n", 22) = 22

Whether or not this explains the trailing ENOTTY errors, whether or not this
is symptom or cause --- I do not know ...

Cheers,
Erich




_______________________________________________
elbe-users mailing list
elbe-users at linutronix.de
https://lists.linutronix.de/mailman/listinfo/elbe-users

----- End forwarded message -----




More information about the elbe-devel mailing list