[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <550DEBF9.9070403@nod.at>
Date: Sat, 21 Mar 2015 23:08:57 +0100
From: Richard Weinberger <richard@....at>
To: Dave Kleikamp <dave.kleikamp@...cle.com>, shaggy@...nel.org
CC: jfs-discussion@...ts.sourceforge.net,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>, lists@...dbynature.de,
ben@...adent.org.uk, stable <stable@...r.kernel.org>,
hmage@...ge.net,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: JFS readdir() issues in stable 3.2
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists