All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@canonical.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Eric Van Hensbergen <ericvh@gmail.com>,
	Ron Minnich <rminnich@sandia.gov>,
	Latchesar Ionkov <lucho@ionkov.net>,
	David Howells <dhowells@redhat.com>,
	Jan Harkes <jaharkes@cs.cmu.edu>,
	"maintainer:CODA FILE SYSTEM" <coda@cs.cmu.edu>,
	Dave Kleikamp <shaggy@kernel.org>,
	Petr Vandrovec <petr@vandrovec.name>,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Chris Dunlop <chris@onthe.net.au>,
	v9fs-developer@lists.sourceforge.net,
	linux-afs@lists.infradead.org, codalist@TELEMANN.coda.cs.cmu.edu,
	jfs-discussion@lists.sourceforge.net, linux-nfs@vger.kernel.org,
	ecryptfs@vger.kernel.org
Subject: Re: [PATCH 1/1] fix d_revalidate oopsen on NFS exports
Date: Thu, 1 Dec 2011 02:02:27 -0600	[thread overview]
Message-ID: <20111201080227.GC495@boyd> (raw)
In-Reply-To: <20111201065024.GB495@boyd>

[-- Attachment #1: Type: text/plain, Size: 400 bytes --]

On 2011-12-01 00:50:25, Tyler Hicks wrote:
> As David mentioned, Al's atomic open patches might solve all of this in
> the future, but I don't know much about that patchset. Is there any
> relevant info you could provide about those patches, Al?

Sorry, Al. I see that you've already provided those details here:

https://lkml.org/lkml/2011/5/12/337

I was unaware of that thread until now.

Tyler



[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2011-12-01  8:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  7:36 [PATCH 1/1] fix d_revalidate oopsen on NFS exports Chris Dunlop
2011-11-21  7:36 ` Chris Dunlop
2011-11-29  8:25 ` Chris Dunlop
2011-11-29  8:25   ` Chris Dunlop
2011-11-29 11:58   ` Myklebust, Trond
2011-11-29 11:58     ` Myklebust, Trond
2011-11-30  7:13     ` Chris Dunlop
2011-11-30  8:54       ` David Howells
2011-11-30  8:54         ` David Howells
2011-12-01  0:47         ` Chris Dunlop
2011-12-01  2:22           ` Dave Kleikamp
2011-12-01  3:33             ` Chris Dunlop
2011-12-01  3:53               ` Dave Kleikamp
2011-12-01  3:53                 ` Dave Kleikamp
2011-12-01  5:32                 ` Chris Dunlop
2011-12-01  5:32                   ` Chris Dunlop
2011-12-01  5:34           ` Chris Dunlop
2011-12-01  5:34             ` Chris Dunlop
2011-12-01  6:31           ` Tyler Hicks
2011-12-01  7:29             ` Chris Dunlop
2011-12-01  7:29               ` Chris Dunlop
2011-12-06 11:43               ` Jacek Luczak
2011-12-01  6:50   ` Tyler Hicks
2011-12-01  7:23     ` Chris Dunlop
2011-12-01  7:23       ` Chris Dunlop
2011-12-01  8:02     ` Tyler Hicks [this message]

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=20111201080227.GC495@boyd \
    --to=tyhicks@canonical.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chris@onthe.net.au \
    --cc=coda@cs.cmu.edu \
    --cc=codalist@TELEMANN.coda.cs.cmu.edu \
    --cc=dhowells@redhat.com \
    --cc=ecryptfs@vger.kernel.org \
    --cc=ericvh@gmail.com \
    --cc=gregkh@suse.de \
    --cc=jaharkes@cs.cmu.edu \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=petr@vandrovec.name \
    --cc=rminnich@sandia.gov \
    --cc=shaggy@kernel.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    --cc=viro@zeniv.linux.org.uk \
    /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.