From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Kleikamp Subject: Re: JFS readdir() issues in stable 3.2 Date: Sat, 21 Mar 2015 16:58:57 -0500 Message-ID: <550DE9A1.1050200@oracle.com> References: <550CAE5C.9010101@nod.at> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: jfs-discussion@lists.sourceforge.net, linux-fsdevel , Al Viro , lists@nerdbynature.de, ben@decadent.org.uk, stable , hmage@hmage.net, "linux-kernel@vger.kernel.org" To: Richard Weinberger , shaggy@kernel.org Return-path: In-Reply-To: <550CAE5C.9010101@nod.at> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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. > > Dave, has your fix some unnamed dependencies which need backporting too? > > Thanks, > //richard Thanks! Shaggy