All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Dave Kleikamp <dave.kleikamp@oracle.com>, shaggy@kernel.org
Cc: jfs-discussion@lists.sourceforge.net,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	lists@nerdbynature.de, ben@decadent.org.uk,
	stable <stable@vger.kernel.org>,
	hmage@hmage.net,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: JFS readdir() issues in stable 3.2
Date: Sat, 21 Mar 2015 23:08:57 +0100	[thread overview]
Message-ID: <550DEBF9.9070403@nod.at> (raw)
In-Reply-To: <550DE9A1.1050200@oracle.com>

Am 21.03.2015 um 22:58 schrieb Dave Kleikamp:
> On 03/20/2015 06:33 PM, Richard Weinberger wrote:
>> Hi!
>>
>> Mainline commit 44512449c0ab368889dd13ae0031fba74ee7e1d2
>> (jfs: fix readdir cookie incompatibility with NFSv4) does not work as expected on 3.2.
>> Maybe on other stable kernels too.
>>
>> UML stumbled over it:
>> https://bugzilla.kernel.org/show_bug.cgi?id=94741
>>
>> If you run the attached readdir.c on a JFS on stable 3.2.51+ readdir() will not
>> increment the directory offset nor return NULL, hence the caller will loop forever.
>> It looks like if the current directory offset is > 0 and you run seekdir(telldir())
>> the next readdir() call will not increment it.
> 
> The backport failed to pass the proper position to filldir() for the .
> and .. entries. I've attached a proposed patch to the above bug.

Thanks for sorting this out! :-)
//richard

      reply	other threads:[~2015-03-21 22:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 23:33 JFS readdir() issues in stable 3.2 Richard Weinberger
2015-03-21 21:58 ` Dave Kleikamp
2015-03-21 22:08   ` Richard Weinberger [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=550DEBF9.9070403@nod.at \
    --to=richard@nod.at \
    --cc=ben@decadent.org.uk \
    --cc=dave.kleikamp@oracle.com \
    --cc=hmage@hmage.net \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=shaggy@kernel.org \
    --cc=stable@vger.kernel.org \
    --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.