From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "Dr. J. Bruce Fields" <bfields@fieldses.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: NFSv4 poops itself
Date: Fri, 27 Jul 2007 13:29:00 -0400 [thread overview]
Message-ID: <1185557340.6586.51.camel@localhost> (raw)
In-Reply-To: <46AA2872.9040800@garzik.org>
On Fri, 2007-07-27 at 13:16 -0400, Jeff Garzik wrote:
> Trond Myklebust wrote:
> > Jeff and Bruce, could you please try to reproduce the problem after
> > either applying patches 001 to 004 or just the single NFS_ALL patch
> > from
> >
> > http://client.linux-nfs.org/Linux-2.6.x/2.6.23-rc1/
>
>
> It's not easily reproducible here. Any hints on triggering the behavior?
I suspect that the problem may involve mixing O_RDWR with O_RDONLY
and/or O_WRONLY file access. Bruce might have a better suggestion,
though.
next prev parent reply other threads:[~2007-07-27 17:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 12:53 NFSv4 poops itself Jeff Garzik
2007-07-27 13:33 ` Trond Myklebust
2007-07-27 17:09 ` Trond Myklebust
2007-07-27 17:16 ` Jeff Garzik
2007-07-27 17:29 ` Trond Myklebust [this message]
2007-08-03 19:13 ` J. Bruce Fields
2007-08-06 13:40 ` J. Bruce Fields
2007-08-06 18:40 ` Trond Myklebust
2007-07-27 18:29 ` Marc Dietrich
2007-07-27 13:36 ` Marc Dietrich
2007-07-27 13:40 ` Jeff Garzik
2007-07-27 14:45 ` Trond Myklebust
2007-07-27 14:58 ` Satyam Sharma
2007-07-27 17:58 ` Marc Dietrich
2007-07-27 18:39 ` Trond Myklebust
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=1185557340.6586.51.camel@localhost \
--to=trond.myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.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.