Linux kernel announcements
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: linux-kernel-announce@vger.kernel.org,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	peter.kovar@gmail.com
Subject: Re: [Bugme-new] [Bug 8966] New: NFSv3 server error in LOOKUP after READDIRPLUS Call
Date: Sun, 2 Sep 2007 14:01:33 -0700	[thread overview]
Message-ID: <20070902140133.a5e7b3d5.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-8966-10286@http.bugzilla.kernel.org/>

> On Sun,  2 Sep 2007 10:55:01 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8966
> 
>            Summary: NFSv3 server error in LOOKUP after READDIRPLUS Call
>            Product: File System
>            Version: 2.5
>      KernelVersion: 2.6.23-rc?
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: NFS
>         AssignedTo: trond.myklebust@fys.uio.no
>         ReportedBy: peter.kovar@gmail.com
> 
> 
> Most recent kernel where this bug did not occur: 2.6.22.6
> Distribution: Fedora release 7.91 (Rawhide)
> Hardware Environment: Intel Core 2 Quad
> Problem Description: ls NFS automounted directory through UDP or TCP returns
> NFS3ERR_NOENT error in LOOKUP reply for directories such as /dev /net /proc 
> 
> Steps to reproduce:
> 
> € ls -l /net/Quad
> total 432
> ?---------    ? ?           ?        ?            ? /net/Quad/boot
> ?---------    ? ?           ?        ?            ? /net/Quad/dev
> ?---------    ? ?           ?        ?            ? /net/Quad/misc
> ?---------    ? ?           ?        ?            ? /net/Quad/net
> ?---------    ? ?           ?        ?            ? /net/Quad/proc
> ?---------    ? ?           ?        ?            ? /net/Quad/sys
> drwxr-xr-x    2 root        root  4096 Aug 31 17:18 bin
> drwxr-xr-x  129 root        root 12288 Sep  2 18:09 etc
> drwxr-xr-x    7 root        root  4096 Aug 21 23:30 home
> 
> It the same in whole 2.6.23-rc? series as well as latest Fedora kernel with
> identical configuration. 2.6.22.6 is OK.
> 
> € uname -a
> Linux Quad 2.6.23-rc1 #1 SMP PREEMPT Sun Sep 2 17:40:25 CEST 2007 x86_64 x86_64
> x86_64 GNU/Linux
> Linux Quad 2.6.23-rc2 #1 SMP PREEMPT Sun Sep 2 14:57:57 CEST 2007 x86_64 x86_64
> x86_64 GNU/Linux
> Linux Quad 2.6.23-rc3 #1 SMP PREEMPT Sun Sep 2 15:01:02 CEST 2007 x86_64 x86_64
> x86_64 GNU/Linux
> Linux Quad 2.6.23-rc4 #1 SMP PREEMPT Sun Sep 2 14:59:25 CEST 2007 x86_64 x86_64
> x86_64 GNU/Linux
> Linux Quad 2.6.23-rc5 #1 SMP PREEMPT Sat Sep 1 12:52:16 CEST 2007 x86_64 x86_64
> x86_64 GNU/Linux
> Linux Quad 2.6.23-0.149.rc4.fc8 #1 SMP Wed Aug 29 07:37:52 EDT 2007 x86_64
> x86_64 x86_64 GNU/Linux
> 
> gcc-4.1.2-19
> binutils-2.17.50.0.18-1
> 

A post-2.6.2 regression.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel-announce" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

           reply	other threads:[~2007-09-02 21:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-8966-10286@http.bugzilla.kernel.org/>]

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=20070902140133.a5e7b3d5.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel-announce@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=peter.kovar@gmail.com \
    --cc=trond.myklebust@fys.uio.no \
    /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