mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wayne Scott <wscott@bitmover.com>
To: viro@math.psu.edu
Cc: cr@sap.com, lm@bitmover.com, janfrode@parallab.uib.no,
	linux-kernel@vger.kernel.org
Subject: Re: Kernel Compile in tmpfs crumples in 2.4.12 w/epoll patch
Date: Mon, 22 Oct 2001 08:29:35 -0500 (EST)	[thread overview]
Message-ID: <20011022.082935.74750744.wscott@bitmover.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0110220556150.2294-100000@weyl.math.psu.edu>
In-Reply-To: <m3pu7gggbf.fsf@linux.local> <Pine.GSO.4.21.0110220556150.2294-100000@weyl.math.psu.edu>

From: Alexander Viro <viro@math.psu.edu>
> > tmpfs does not know anything about directory handling. It uses
> > generic_read_dir and dcache_readdir. So this must be a bug in the vfs
> > layer. Al, what do you say?
> 
> If you are changing directory between the calls of getdents(2) - you have
> no warranty that offsets will stay stable.  It's not just Linux.
> 
> Frankly, I don't see what could be done, short of doing qsort() by inumber
> or something equivalent...

So if I am adding files while reading the directory the directory
structure gets rewritten and I might return files more than once?
What happens if files are being deleted?  Can files be skipped?!?

Any reason we have never seen this on ext2 on other filesystems on 10+
versions of UNIX?  BitKeeper is pretty paranoid and includes a lot of
sanity checks.

Does this only happen when the subdirectory I am reading changes, or
on tmpfs will changing any directory cause this?

I am looking at coding a workaround, but I need to know how bad the
problem can be.

-Wayne

  parent reply	other threads:[~2001-10-22 13:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-19  0:06 David E. Weekly
2001-10-19  0:22 ` Davide Libenzi
2001-10-19  1:26   ` safemode
2001-10-19  5:12     ` Daniel T. Chen
2001-10-19  8:28 ` Christoph Rohland
2001-10-20 15:17   ` Jan-Frode Myklebust
2001-10-21  8:25     ` Christoph Rohland
2001-10-21 10:07       ` Jan-Frode Myklebust
2001-10-20 22:35         ` wild pointer!!!!! Kalyan
2001-10-21 12:15         ` Kernel Compile in tmpfs crumples in 2.4.12 w/epoll patch safemode
2001-10-21 12:21         ` wild pointer!!!!! Paul Mackerras
     [not found]         ` <E15vHVx-0001Nc-00@ii.uib.no>
2001-10-21 12:34           ` Kernel Compile in tmpfs crumples in 2.4.12 w/epoll patch Jan-Frode Myklebust
2001-10-21 12:53             ` safemode
     [not found]             ` <E15vI6n-0001oC-00@ii.uib.no>
2001-10-21 13:10               ` bk regression fails on tmpfs /tmp, was: " Jan-Frode Myklebust
2001-10-21 13:36                 ` safemode
2001-10-21 16:35       ` Larry McVoy
2001-10-21 17:50         ` Linus Torvalds
2001-10-21 20:15           ` Daniel Phillips
2001-10-22 17:03           ` bill davidsen
2001-10-22 17:12             ` Larry McVoy
2001-10-22 17:29               ` Alexander Viro
2001-10-23  5:25               ` Keith Owens
2001-10-22  9:44         ` Christoph Rohland
2001-10-22 10:01           ` Alexander Viro
2001-10-30 17:29             ` Theodore Tso
2001-10-22 13:29           ` Wayne Scott [this message]
2001-10-22 17:31             ` bill davidsen

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=20011022.082935.74750744.wscott@bitmover.com \
    --to=wscott@bitmover.com \
    --cc=cr@sap.com \
    --cc=janfrode@parallab.uib.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=viro@math.psu.edu \
    /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

Powered by JetHome