From: Christian Storm <christian.storm@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] isar-image-base: fix some dangling mounts
Date: Mon, 13 Nov 2017 13:57:45 +0100 [thread overview]
Message-ID: <20171113125745.fkuixp4wzt7oqyhk@MD1KR9XC.ww002.siemens.net> (raw)
In-Reply-To: <4c30798e-62b8-6252-25fb-f7e680213bec@ilbers.de>
> > As bitbake/lib/bb/build.py's shell_trap_code() injects
> > `set -e` into scripts, the premature end of scripts leaves
> > dangling mounts around. Fix these dangling mounts by hooking
> > into the EXIT trap handler also setup by shell_trap_code().
>
> Could you please specify which mounts are dangling and how you
> reproduce this?
All those now supervised by the trap. To reproduce, e.g., for
meta/recipes-devtools/buildchroot/buildchroot.bb, put a
false
after, e.g., the trap line simulating the following multistrap call to
have failed. Then, without this patch, ${BUILDCHROOT_DIR}/proc is still
mounted. With this patch, it's unmounted.
Same procedure applies to the other cases.
Kind regards,
Christian
--
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Otto-Hahn-Ring 6, 81739 M�nchen, Germany
next prev parent reply other threads:[~2017-11-13 12:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 12:22 Christian Storm
2017-11-13 12:50 ` Alexander Smirnov
2017-11-13 12:57 ` Christian Storm [this message]
2017-11-13 13:53 ` Alexander Smirnov
2017-11-13 14:24 ` Christian Storm
2017-11-13 14:47 ` Alexander Smirnov
2017-11-14 7:36 ` Christian Storm
2017-11-14 7:48 ` Alexander Smirnov
2017-11-14 8:58 ` Christian Storm
2017-11-13 13:57 ` Henning Schild
2017-11-14 16:01 ` Alexander Smirnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171113125745.fkuixp4wzt7oqyhk@MD1KR9XC.ww002.siemens.net \
--to=christian.storm@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox