From: Jens Rottmann <JRottmann@LiPPERTEmbedded.de>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: "r/o bind mounts" patch in 2.6.26-rc6 changes (breaks?) error behaviour
Date: Fri, 20 Jun 2008 18:14:56 +0200 [thread overview]
Message-ID: <485BD780.5090103@LiPPERTEmbedded.de> (raw)
In-Reply-To: <1213975689.7512.36.camel@nimitz>
Dave Hansen wrote:
> ... requires a path walk ...
... which is spared only in the error path, the normal path still does the path walk anyway.
> Don't you *want* warnings when an 'rm -f' runs into a r/o filesystem? ;)
Well, not really. The "rm -f"s are in my startup scripts, supposed to delete stale lock files and lots of stuff that's usually not there unless something went wrong the last time. But most of the time, I leave the whole system mounted R/O, except some tmpfs, dead useful for kernel/hardware hacking/testing.
But now I get masses of error messages on bootup - guess I have to litter the scripts with "if [ -e ... ]; then"s or just live with it. :-|
Anyway, thanks for solving this mystery for me. :-)
Jens
next prev parent reply other threads:[~2008-06-20 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <485B8361.6010708@LiPPERTEmbedded.de>
2008-06-20 14:17 ` "r/o bind mounts" patch in 2.6.26-rc6 changes (breaks?) error behaviour Dave Hansen
2008-06-20 15:28 ` Dave Hansen
2008-06-20 16:14 ` Jens Rottmann [this message]
2008-06-24 18:21 ` Pavel Machek
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=485BD780.5090103@LiPPERTEmbedded.de \
--to=jrottmann@lippertembedded.de \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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