From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753389Ab1IUL46 (ORCPT ); Wed, 21 Sep 2011 07:56:58 -0400 Received: from lucidpixels.com ([72.73.18.11]:48907 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752794Ab1IUL45 (ORCPT ); Wed, 21 Sep 2011 07:56:57 -0400 Date: Wed, 21 Sep 2011 07:56:57 -0400 (EDT) From: Justin Piszcz To: Jeff Layton cc: Suresh Jayaraman , linux-kernel@vger.kernel.org, linux-cifs Subject: Re: 3.1-rc4: CIFS VFS: Received no data, expecting 4 In-Reply-To: <20110921075730.74c3b512@corrin.poochiereds.net> Message-ID: References: <4E79C958.7080702@suse.com> <20110921075730.74c3b512@corrin.poochiereds.net> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 21 Sep 2011, Jeff Layton wrote: > On Wed, 21 Sep 2011 16:54:08 +0530 > Suresh Jayaraman wrote: > >> Adding linux-cifs@vger.kernel.org to Cc. >> >> On 09/18/2011 10:29 PM, Justin Piszcz wrote: >>> Hello, >>> >>> What does this mean and why does it occur? >> >> This error seems to occur when we try to read from a socket and actually >> read no data. Not sure when this would occur. >> > > It would be nice to know what was returned by kernel_recvmsg here. Was > it "0" or an error code of some kind? Hi, It seemed to start like that: Sep 18 12:02:52 p34 kernel: [ 71.039405] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Sep 18 12:02:52 p34 kernel: [ 71.039970] NFSD: starting 90-second grace period Sep 18 12:17:06 p34 kernel: [ 923.377483] CIFS VFS: Received no data, expecting 4 Sep 18 12:17:23 p34 kernel: [ 940.991731] [drm] nouveau 0000:04:00.0: Setting dpms mode 3 on tmds encoder (output 1) Sep 18 12:18:23 p34 kernel: [ 1000.699094] CIFS VFS: Received no data, expecting 4 Sep 18 12:18:53 p34 kernel: [ 1030.668222] CIFS VFS: Received no data, expecting 4 Sep 18 12:19:23 p34 kernel: [ 1060.637386] CIFS VFS: Received no data, expecting 4 Sep 18 12:19:53 p34 kernel: [ 1090.606501] CIFS VFS: Received no data, expecting 4 Sep 18 12:20:23 p34 kernel: [ 1120.575675] CIFS VFS: Received no data, expecting 4 Sep 18 12:20:53 p34 kernel: [ 1150.544783] CIFS VFS: Received no data, expecting 4 Sep 18 12:21:23 p34 kernel: [ 1180.513925] CIFS VFS: Received no data, expecting 4 Sep 18 12:21:53 p34 kernel: [ 1210.483044] CIFS VFS: Received no data, expecting 4 Sep 18 12:22:23 p34 kernel: [ 1240.452187] CIFS VFS: Received no data, expecting 4 Sep 18 12:22:53 p34 kernel: [ 1270.421345] CIFS VFS: Received no data, expecting 4 Sep 18 12:23:23 p34 kernel: [ 1300.390432] CIFS VFS: Received no data, expecting 4 Sep 18 12:23:53 p34 kernel: [ 1330.359595] CIFS VFS: Received no data, expecting 4 Sep 18 12:24:23 p34 kernel: [ 1360.328755] CIFS VFS: Received no data, expecting 4 Sep 18 12:24:53 p34 kernel: [ 1390.283901] CIFS VFS: Received no data, expecting 4 Sep 18 12:25:23 p34 kernel: [ 1420.249492] CIFS VFS: Received no data, expecting 4 Sep 18 12:25:53 p34 kernel: [ 1450.218690] CIFS VFS: Received no data, expecting 4 Sep 18 12:26:23 p34 kernel: [ 1480.187842] CIFS VFS: Received no data, expecting 4 Sep 18 12:26:53 p34 kernel: [ 1510.156925] CIFS VFS: Received no data, expecting 4 Sep 18 12:27:23 p34 kernel: [ 1540.126080] CIFS VFS: Received no data, expecting 4 Sep 18 12:27:54 p34 kernel: [ 1570.095264] CIFS VFS: Received no data, expecting 4 Justin.