linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Karl Schmidt <karl@xtronics.com>,
	Jonathan McDowell <noodles@earth.li>,
	jfs-discussion@lists.sourceforge.net,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Ben Hutchings <ben@decadent.org.uk>,
	linux-nfs@vger.kernel.org
Subject: Re: [Jfs-discussion] [PATCH] jfs: fix readdir cookie incompatibility with NFSv4
Date: Mon, 26 Aug 2013 17:27:47 -0500	[thread overview]
Message-ID: <521BD663.9070805@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1308241517240.21301@trent.utfs.org>

On 08/24/2013 05:21 PM, Christian Kujau wrote:
> On Thu, 15 Aug 2013 at 15:48, Dave Kleikamp wrote:
>> This patch replaces the one I posted yesterday. I like this better since
>> it doesn't require fixing existing on-disk cookies or skipping a
>> position in the in-inode index table.
>>
>> NFSv4 reserves readdir cookie values 0-2 for special entries (. and ..),
>> but jfs allows a value of 2 for a non-special entry. This incompatibility
>> can result in the nfs client reporting a readdir loop.
>>
>> This patch doesn't change the value stored internally, but adds one to
>> the value exposed to the iterate method.
> 
> Out of curiosity, will this land on 3.11?

Just sent a pull request to Linus. Once it's picked up, I'll submit a
patch to the stable trees.

  reply	other threads:[~2013-08-26 22:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08  1:13 NFS 'readdir loop' error on JFS Ben Hutchings
2013-07-08 14:02 ` bjschuma
2013-07-08 15:43 ` Karl Schmidt
2013-08-09 20:44 ` Karl Schmidt
2013-08-10  7:28   ` [Jfs-discussion] " Christian Kujau
2013-08-10 19:43     ` Karl Schmidt
2013-08-12  8:18     ` Christian Kujau
2013-08-12  8:29       ` Christian Kujau
2013-08-12 16:29         ` J. Bruce Fields
2013-08-12 20:04           ` Christian Kujau
2013-08-15  3:54           ` [PATCH] jfs: avoid misuse of cookie value of 2 Dave Kleikamp
2013-08-15  4:29             ` Christian Kujau
2013-08-15  7:09               ` Christian Kujau
2013-08-15 13:38                 ` Dave Kleikamp
2013-08-15 20:48                 ` [PATCH] jfs: fix readdir cookie incompatibility with NFSv4 Dave Kleikamp
2013-08-15 21:26                   ` Christian Kujau
2013-08-15 22:09                     ` Dave Kleikamp
2013-08-17 20:01                     ` Ben Hutchings
2013-08-19 19:11                       ` [JunkMail] " ben
2013-08-29 22:48                       ` Jonathan McDowell
2013-09-05  3:40                         ` Bug#714974: " Jonathan McDowell
2013-08-24 22:21                   ` [Jfs-discussion] " Christian Kujau
2013-08-26 22:27                     ` Dave Kleikamp [this message]
2013-08-15 13:38             ` [PATCH] jfs: avoid misuse of cookie value of 2 J. Bruce Fields

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=521BD663.9070805@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=ben@decadent.org.uk \
    --cc=bfields@fieldses.org \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=karl@xtronics.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=noodles@earth.li \
    /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;
as well as URLs for NNTP newsgroup(s).