From: Steve Kenton <skenton@ou.edu>
To: buildroot@busybox.net
Subject: [Buildroot] Obscure bug in Util-Linux umount?
Date: Tue, 10 Mar 2015 11:16:20 -0500 [thread overview]
Message-ID: <54FF18D4.2030709@ou.edu> (raw)
In-Reply-To: <54FE7E8E.20306@ou.edu>
On 03/10/2015 12:18 AM, Steve Kenton wrote:
> I *think* this is an obscure bug in the util-linux version of umount, but I wonder if anyone else has run into it. It drove me nuts for a while. Here's a short description.
Further testing revealed that it only occurs if the embedded root filesystem is read-only
which I forgot to mention (blush) so it's probably an interaction with a stale /etc/mtab
or something, but only for the root filesystem and only if the mount point directory names
are the same, yada etc. Much less likely to bite anyone else so I guess a heads up is not needed.
Any way, not really a bug but rather a feature with undefined behaviour and most importantly
a case of 'it hurts if I do this' soooo 'don't do that'!
Sorry for the noise.
Steve
next prev parent reply other threads:[~2015-03-10 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54FE7E8E.20306@ou.edu>
2015-03-10 5:25 ` [Buildroot] Obscure bug in Util-Linux umount? Steve Kenton
2015-03-10 16:16 ` Steve Kenton [this message]
2015-03-10 17:59 ` Thomas Petazzoni
2015-03-10 18:05 ` Steve Kenton
2015-03-12 0:50 ` [Buildroot] Obscure bug in Util-Linux umount? - Solved Steve Kenton
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=54FF18D4.2030709@ou.edu \
--to=skenton@ou.edu \
--cc=buildroot@busybox.net \
/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