From: Willy Tarreau <willy@w.ods.org>
To: herbert@13thfloor.at, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bind Mount Extensions 0.04
Date: Mon, 15 Mar 2004 23:04:53 +0100 [thread overview]
Message-ID: <20040315220453.GA19556@alpha.home.local> (raw)
In-Reply-To: <20040315053654.GA31818@MAIL.13thfloor.at>
Hi Herbert,
On Mon, Mar 15, 2004 at 06:36:55AM +0100, Herbert Poetzl wrote:
> > # mount /dev/hdaXX /mnt/disk
> > # mount -r --bind /mnt/disk /mnt/ro
> > # touch /mnt/ro/foo
> > Read-only file-system (that's what was expected)
> > # umount /mnt/ro
> > (I don't remember if the problem already arises here)
> > # umount /mnt/disk
> > device is busy
>
> this has been fixed in 0.04 for 2.4.25, if you need
> the fix to include for 0.03 (for whatever reason)
> here is the relevant hunk ..
I can confirm that it now works perfectly, as expected.
Thank you very much,
Willy
prev parent reply other threads:[~2004-03-15 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 3:53 [PATCH] Bind Mount Extensions 0.04 Herbert Poetzl
[not found] ` <20040315045952.GD14537@alpha.home.local>
2004-03-15 5:36 ` Herbert Poetzl
2004-03-15 22:04 ` Willy Tarreau [this message]
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=20040315220453.GA19556@alpha.home.local \
--to=willy@w.ods.org \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
/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