Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Kenton <skenton@ou.edu>
To: buildroot@busybox.net
Subject: [Buildroot] Obscure bug in Util-Linux umount?
Date: Tue, 10 Mar 2015 13:05:45 -0500	[thread overview]
Message-ID: <54FF3279.80403@ou.edu> (raw)
In-Reply-To: <20150310185937.280f8497@free-electrons.com>

On 3/10/2015 12:59 PM, Thomas Petazzoni wrote:
> Dear Steve Kenton,
>
> On Tue, 10 Mar 2015 11:16:20 -0500, Steve Kenton wrote:
>
>> 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'!
> Interesting. After reading your e-mail, I had a very quick look at the
> kernel side and util-linux side, looking for code using the
> s_last_mounted field of the superblock which indeed contains the last
> location where it was mounted. But I couldn't spot any place where it
> is specifically used to prevent something from happening. But I didn't
> spend a lot of time, so I may very well have missed something.
>
> Thomas
If anyone else has ever hit this then it might be worth pursuing and 
I'll take another look,
but if nobody else cares I'll just chock it up to dumb-(bad)-luck and 
move along.

Any one out there care about this? It's easy for me to reproduce right 
now while (painfully) fresh in my memory.

Steve

  reply	other threads:[~2015-03-10 18:05 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
2015-03-10 17:59   ` Thomas Petazzoni
2015-03-10 18:05     ` Steve Kenton [this message]
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=54FF3279.80403@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