linux-kernel - Re: [bisect] kernel 2.6.38 regression with root nfs mounting

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 29 Mar 2011 16:24:08 -0400
From:	"Will Simoneau" <simoneau@....uri.edu>
To:	Chuck Lever <chuck.lever@...cle.com>
Cc:	Belisko Marek <marek.belisko@...il.com>,
	Trond.Myklebust@...app.com, broonie@...nsource.wolfsonmicro.com,
	bdowning@...os.net, linux-nfs@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [bisect] kernel 2.6.38 regression with root nfs mounting

On 09:26 Fri 25 Mar     , Chuck Lever wrote:
> 
> According to the trace, the mount succeeds, and NFS requests are working.  However, the server's replies to READ requests are not being seen by the client.  Something on the client host or in the network is dropping them.  I see successful 16KB reads, but 32KB reads do not work.  Check your client for packet filtering (either intentional filtering, or accidental filtering due to configuration issues).
> 
> I'll revisit the mount option defaults for NFSROOT again.

I have encountered the same problem as Belisko, using an FPGA board I am
working on (CPU is a mipsel r4k clone). 2.6.38-rc8 nfsroot works fine,
2.6.38 hangs while starting init. I can see read replies going out from
the NFS server but the client does not seem to receive them.

Interestingly, we are both using DM9000 network chips. I wonder if there
is a UDP-related problem on the DM9000. I will play with my
configuration a little more (in particular testing proto=tcp and revert
of 53d4737580535e073963b91ce87d4216e434fab5) but my guess is the DM9000
driver/chip is to blame. The DM9000A on my board has 16K of on-chip SRAM
used for its RX/TX buffers which may be playing a part in the problem.

Content of type "application/pgp-signature" skipped