linux-kernel - Re: 2.6.28-rc3 truncates nfsd results

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20081109190951.GD25568@fieldses.org>
Date:	Sun, 9 Nov 2008 14:09:51 -0500
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Doug Nazar <nazard@...goninc.ca>,
	'David Woodhouse' <David.Woodhouse@...el.com>,
	'Al Viro' <viro@...iv.linux.org.uk>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.28-rc3 truncates nfsd results

On Tue, Nov 04, 2008 at 01:43:38PM -0500, Jeff Garzik wrote:
> Doug Nazar wrote:
>> Commit 8d7c4203 "nfsd: fix failure to set eof in readdir in some situations"
>> breaks the nfsd server. Bisected it back to this commit and reverting it
>> fixes the problem.
>>
>> However, it only happens on certain machines even with the same kernel &
>> filesystem (ext3). I've two groups of similar computers, each group running
>> identical kernels. The ones listing only ~250 files are of course in error.
>> Eldritch is running 2.6.28-rc3 with that commit reverted. With 2.8.28-rc3 it
>> showed the incorrect number.
>
> I'm seeing "weirdness" on my NFS4-mounted home directory (client and  
> server are both x86-64 2.6.28-rc) -- gconfd locking up, and other  
> desktop gadgets breaking.  2.6.27 works great.
>
> I'll try reverting this and see if the behavior improves, thanks for the  
> pointer...

Any more details on that "weirdness"?

--b.
--
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/