All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Larry McVoy <lm@bitmover.com>, Alexander Viro <viro@math.psu.edu>
Cc: Jan-Frode Myklebust <janfrode@parallab.uib.no>,
	ML-linux-kernel <linux-kernel@vger.kernel.org>,
	Wayne Scott <wscott@bitmover.com>
Subject: Re: Kernel Compile in tmpfs crumples in 2.4.12 w/epoll patch
Date: 22 Oct 2001 11:44:04 +0200	[thread overview]
Message-ID: <m3pu7gggbf.fsf@linux.local> (raw)
In-Reply-To: <016a01c15831$ef51c5c0$5c044589@legato.com> <m33d4gjaoa.fsf@linux.local> <20011020171730.A28057@parallab.uib.no> <3BD28673.1060302@sap.com> <20011021093547.A24227@work.bitmover.com>
In-Reply-To: <20011021093547.A24227@work.bitmover.com>

Hi Larry,

On Sun, 21 Oct 2001, Larry McVoy wrote:
> One of the engineers here has also seen this.  The root cause is
> that readdir() is returning a file multiple times.  We've seen it on
> tmpfs.  We also have seen in in NFS and had a workaround, the
> workaround depended that the file would be returned twice right next
> to each other and that's not the case in tmpfs.  wscott@bitmover.com
> can provide you with the details of his machine config, here's the
> mail he sent a while back about it:

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?

Greetings
		Christoph



  parent reply	other threads:[~2001-10-22  9:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-19  0:06 Kernel Compile in tmpfs crumples in 2.4.12 w/epoll patch 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:21           ` Paul Mackerras
2001-10-21 12:15         ` Kernel Compile in tmpfs crumples in 2.4.12 w/epoll patch safemode
     [not found]         ` <E15vHVx-0001Nc-00@ii.uib.no>
2001-10-21 12:34           ` 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 [this message]
2001-10-22 10:01           ` Alexander Viro
2001-10-22 13:29             ` Wayne Scott
2001-10-22 17:31               ` bill davidsen
2001-10-30 17:29             ` Theodore Tso

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=m3pu7gggbf.fsf@linux.local \
    --to=cr@sap.com \
    --cc=janfrode@parallab.uib.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=viro@math.psu.edu \
    --cc=wscott@bitmover.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.