mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Welles <mikewelles71@yahoo.com>
To: Christoph Hellwig <hch@infradead.org>, Juergen Hasch <lkml@elbonia.de>
Cc: Michael Welles <mike@bangstate.com>, linux-kernel@vger.kernel.org
Subject: Re: Using get_cwd inside a module.
Date: Sat, 22 Nov 2003 09:22:53 -0800 (PST)	[thread overview]
Message-ID: <20031122172253.5645.qmail@web41906.mail.yahoo.com> (raw)
In-Reply-To: <20031122110459.A31359@infradead.org>

For changedfiles, using cut n' paste sys_getcwd, we've
managed to get "good enough" functionality.  When a
user runs "touch foo" in /tmp/watch, when we intercept
the  openw, we manage to resolve "foo" to
"/tmp/watch/foo".   We still break on things like 
"touch ../../foo", since we resolve that to
"/tmp/watch/../../foo"  -- but that's pretty fixable  
with a little effort.

NFS mounted filesystems still get us, since we rely on
intercepting the system calls and putting a wrapper
around them.  I've looked into doing so, but I didn't
see a way of doing so in a module -- and we haven't
wanted to demand that users patch and rebuild a
kernel.


--- Christoph Hellwig <hch@infradead.org> wrote:

> 
> Well, reporting a single path component relative to
> the parent directory
> is doable, there's just no way to have a canonical
> absolute or
> multi-component pathname.
> 


__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

  reply	other threads:[~2003-11-22 17:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-22  0:05 Michael Welles
2003-11-22  0:32 ` Maciej Zenczykowski
2003-11-22 12:30   ` Szymon Acedański
2003-11-22  8:30 ` Christoph Hellwig
2003-11-22  9:33   ` Juergen Hasch
2003-11-22 10:15     ` Christoph Hellwig
2003-11-22 10:45       ` Juergen Hasch
2003-11-22 11:04         ` Christoph Hellwig
2003-11-22 17:22           ` Michael Welles [this message]
2003-11-23 19:40           ` Juergen Hasch
2003-11-22 11:48       ` Andreas Dilger
2003-11-23 19:41         ` Juergen Hasch
2003-11-22 17:15       ` Michael Welles

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=20031122172253.5645.qmail@web41906.mail.yahoo.com \
    --to=mikewelles71@yahoo.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@elbonia.de \
    --cc=mike@bangstate.com \
    /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

all inboxes | Powered by JetHome®