From: Andreas Schwab <schwab@suse.de>
To: Ian Kent <raven@themaw.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: umount -l <path>, getcwd and /proc/<pid>/cwd inconsistent
Date: Mon, 07 Jan 2008 11:37:15 +0100 [thread overview]
Message-ID: <jemyrhaplw.fsf@sykes.suse.de> (raw)
In-Reply-To: <1199675850.3156.15.camel@raven.themaw.net> (Ian Kent's message of "Mon\, 07 Jan 2008 12\:17\:30 +0900")
Ian Kent <raven@themaw.net> writes:
> Basically, from a bash shell, setting working directory to a mounted
> directory all is fine with "pwd" and "/proc/<pid>/cwd". Following a
> "umount - l" on the mount "pwd" continues to return the expected string
> but "/proc/<pid>/cwd" returns an empty string.
Builtin pwd just prints $PWD.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-01-07 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 3:17 umount -l <path>, getcwd and /proc/<pid>/cwd inconsistent Ian Kent
2008-01-07 8:29 ` Bauke Jan Douma
2008-01-07 8:55 ` Ian Kent
2008-01-07 9:29 ` Ian Kent
2008-01-07 10:37 ` Andreas Schwab [this message]
2008-01-09 3:10 ` Ian Kent
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=jemyrhaplw.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.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;
as well as URLs for NNTP newsgroup(s).