linux-kernel - Re: Odd log message associated with NFS

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070328185534.GA585@ds20.borg.net>
Date:	Wed, 28 Mar 2007 18:55:34 +0000
From:	Thorsten Kranzkowski <dl8bcu@...bcu.de>
To:	Neil Brown <neilb@...e.de>
Cc:	Phy Prabab <phyprabab@...il.com>, nfs@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: Re: Odd log message associated with NFS

On Wed, Mar 28, 2007 at 12:19:52PM +1000, Neil Brown wrote:
> On Tuesday March 27, dl8bcu@...bcu.de wrote:
> > On Tue, Mar 27, 2007 at 11:40:48AM -0700, Phy Prabab wrote:
> > > kernel: rpcsvc: received unknown control message:-2144992132/-1
> > 
> > Just a 'me, too':
> 
> For the 'unknown control message' messages,
> see:   "fix typo in svc_udp_recvfrom"  previously on
> nfs@...ts.sourceforge.net.
> 
> Fix is in -mm and below.

will try, thanks.
 
> For "svc: bad direction" .... Don't know... garbage on the net maybe?
> Or maybe not.  I have seen something like that before, but haven't

I don't think so as it would mean corruption at other places, too. The
Network is quite uninteresting: single ethernet segment, 2 switches
involved, longest cable 8 meters ...

> been able to pin it on anything yet.
> NeilBrown

I _had_ problems with the previous kernel (same version, same config, 
different (older) compiler (gcc 3.4.5 instead of 4.1.2), on both client and server)
It would randomly (usually within 30 mins) 'lock up' NFS, where the client
sends out requests but doesn't get any answer (apart from tcp-ack) from the 
server. Only a forced umount/remount recovered that (until the next lock-up). 
But I'm willing to attribute that to a somehow broken gcc.

again, thanks for commenting.

bye,
Thorsten
 
> --- linux-2.6.orig/net/sunrpc/svcsock.c
> +++ linux-2.6/net/sunrpc/svcsock.c
> @@ -779,7 +779,7 @@ svc_udp_recvfrom(struct svc_rqst *rqstp)
>  	}
>  
>  	clear_bit(SK_DATA, &svsk->sk_flags);
> -	while ((err == kernel_recvmsg(svsk->sk_sock, &msg, NULL,
> +	while ((err = kernel_recvmsg(svsk->sk_sock, &msg, NULL,
>  				      0, 0, MSG_PEEK | MSG_DONTWAIT)) < 0 ||
>  	       (skb = skb_recv_datagram(svsk->sk_sk, 0, 1, &err)) == NULL) {
>  		if (err == -EAGAIN) {
> 
> 
> > 
> > Mar 16 16:57:06 Marvin kernel: svc: bad direction 268435456, dropping request
> > Mar 16 17:58:19 Marvin kernel: svc: bad direction 268435456, dropping request
> > Mar 16 19:55:49 Marvin kernel: svc: bad direction 268435456, dropping request
> > ...
> > Mar 17 04:30:03 Marvin kernel: svc: bad direction 268435456, dropping request

-- 
| Thorsten Kranzkowski        Internet: dl8bcu@...bcu.de                      |
| Mobile: ++49 170 1876134       Snail: Kiebitzstr. 14, 49324 Melle, Germany  |
| Ampr: dl8bcu@...lj.#rpl.deu.eu, dl8bcu@...vin.dl8bcu.ampr.org [44.130.8.19] |
-
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/