From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6548708150105604096 X-Received: by 2002:a1c:96ca:: with SMTP id y193-v6mr942873wmd.16.1527174639680; Thu, 24 May 2018 08:10:39 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:3acd:: with SMTP id h196-v6ls3661814wma.12.canary-gmail; Thu, 24 May 2018 08:10:39 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrkRG2bLYl4TlCJAdXslfTELm9VjH3y2TvgWIyEIAo2yOv4h3tUpRTBCGQadeDDEtHUcaiy X-Received: by 2002:a1c:8985:: with SMTP id l127-v6mr950528wmd.24.1527174639284; Thu, 24 May 2018 08:10:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527174639; cv=none; d=google.com; s=arc-20160816; b=QV4ct91+6xZBd47Em6OahIqTF6ZrZgEELqjiPxRFjX6bPB3JVCM5GFI+KMmZUdao3N Ulkl3dDSttDaGYKc+tGP4rQ676XAzk3Ex2sqexmhGQjmNMQ1WhNLJPhfuTFjWvWlQEWa rs2QNSAfrgTVjlNzHfufxxc4aRJ2cvOU8sG5z8oLYZnjNBuZAlSP3rrEJj1aYkjimyHl z3gthH8OzqzJ6hfSuMFGh89GlTMa6keYgTvoFCkePiKFNbCkqvGzrkUO0qTo64qGYSC1 khPTNUETqP5LwsxVh++rBapz4J854C9De9ZhnUYNr8V6Gj/x73FTZ+I+l4oQ9ZargmzV 5oLA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:arc-authentication-results; bh=uLHOvOkCwP/8d4FqeeYDdUnPNILUuRExYrnFIaouL0U=; b=QWJqauabkw8Cs67vdHUrYDnge/ZSY7MlwYwm4P8ZFN3jwt6vLkJozW8K8vAB34SYfA 8IifmP1Fh2XYoS4Aw8LyeIeQe/fgf9sRB+Rfxe/AXZK05Ul6/erVzXCaVoxPCGph/Hlr wUiBEswJ2vR+cK0Cb8sGRKagPQCa+77F0YeeWvungijYiGIZsh65/Hnwiq0dvzqb8bCt TGwqH1+jOShXVMugKYuP25rSkIVT5UJHHJJaaaWMQPZrwKv74eHDYFLOU6G4szqS+JBi AysOWssTOLm+LXrXyR8m3I3v+WI9lOs6jBQXwFl6BaS4G1q+RqNaeLg3XDUtNr3uJCET lnBg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id d18-v6si280062wrm.0.2018.05.24.08.10.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 May 2018 08:10:39 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w4OFAchh008377 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 24 May 2018 17:10:38 +0200 Received: from md1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40]) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w4OFAcuJ013125; Thu, 24 May 2018 17:10:38 +0200 Date: Thu, 24 May 2018 17:10:37 +0200 From: Henning Schild To: "[ext] Claudius Heine" Cc: Jan Kiszka , Alexander Smirnov , isar-users Subject: Re: Overview over my outstanding patches Message-ID: <20180524171037.24fea66f@md1pvb1c.ad001.siemens.net> In-Reply-To: References: <988a13f4-5a03-0ca5-7b68-8b95d91fc222@ilbers.de> <1e1bc52c-05bc-2b75-ed50-b41b571cdbfb@siemens.com> <9b19e51b-7ddc-e1c3-9aef-e48f89c01563@siemens.com> <854a4c57-6716-6e88-ba23-846d86d23243@siemens.com> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-TUID: RXbxJtOPXyXM Am Thu, 24 May 2018 17:02:09 +0200 schrieb "[ext] Claudius Heine" : > On 2018-05-24 16:52, Jan Kiszka wrote: > > On 2018-05-24 16:50, Claudius Heine wrote: =20 > >> Hi Jan, > >> > >> On 2018-05-24 15:38, Jan Kiszka wrote: =20 > >>> On 2018-05-24 15:34, [ext] Claudius Heine wrote: =20 > >>>> Hi, > >>>> > >>>> On 2018-05-24 11:21, [ext] Claudius Heine wrote: =20 > >>>>> Hi Alex, > >>>>> > >>>>> On 2018-05-14 15:47, Alexander Smirnov wrote: =20 > >>>>>> Remaining: > >>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>>>> =C2=A0=C2=A0=C2=A0- meta-isar/isar-image-base: added removal of q= emu-*-static > >>>>>> binaries: > >>>>>> > >>>>>> Here is the question about case, when user wants to install > >>>>>> qemu-user-static package to target rootfs. =20 > >>>>> > >>>>> If the user wants to install qemu-user-static to the image, apt > >>>>> overwrites the one already there and then the linux kernel > >>>>> complains about infinite symlink since it wants to execute the > >>>>> new foreign 'qemu-*-static' binary with the foreign > >>>>> 'qemu-*-static' binary on and on. > >>>>> > >>>>> Installing qemu-user-static is simply forbidden until > >>>>> qemu-debootstrap changes the deployment path and binfmt > >>>>> settings to avoid this conflict. =20 > >>>> > >>>> With Hennings help we further investigated this. The binfmt_misc > >>>> flag 'F' would prevent this issue [1]. So installing > >>>> qemu-user-static could be possible if that flag is used. =20 > >>> > >>> Do we have that under our control, or would we have to patch the > >>> upstream binfmt debian package to tune that flag? =20 > >> > >> I have to investigate that. On my sid debian host that flag was > >> set. I think I can see this in the diff between > >> the /var/lib/binfmts/qemu-arm from the kas container and my host: > >> > >> --- kas-qemu-arm=C2=A0=C2=A0=C2=A0 2018-05-24 16:48:31.998958282 +0200 > >> +++ /var/lib/binfmts/qemu-arm=C2=A0=C2=A0=C2=A0 2018-05-22 15:02:13.58= 0660019 > >> +0200 @@ -7,3 +7,4 @@ > >> > >> =C2=A0yes > >> > >> +yes > >> > >> I suppose this yes is were the 'F' flag is set. Currently I don't > >> know how those files are generated. I can take a look into it. =20 > >=20 > > There is the binfmt-support package, and its update-binfmts seems > > to set that stuff. =20 >=20 > This I know. But were are those qemu configurations defined? Is there > a way to overwrite them in order to update those flags? I will have > to investigate how to do that. Maybe we can patch this into those kas=20 > containers. I am not sure the benefit is really worth the complexity. If we mess with binfmt in the containers, one will need to build using this container. And the host might end up in a state it does not expect. And all for installing a package that probably nobody wants. Deleting the qemu is important, for size and clearing reasons. Henning > Claudius >=20