From: Jeff Layton <jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org>
To: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
Cc: Justin Piszcz <jpiszcz-BP4nVm5VUdNhbmWW9KSYcQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: 3.1-rc4: CIFS VFS: Received no data, expecting 4
Date: Wed, 21 Sep 2011 07:57:30 -0400 [thread overview]
Message-ID: <20110921075730.74c3b512@corrin.poochiereds.net> (raw)
In-Reply-To: <4E79C958.7080702-IBi9RG/b67k@public.gmane.org>
On Wed, 21 Sep 2011 16:54:08 +0530
Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org> wrote:
> Adding linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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?
> > (mounted a Windows 7 share)
> >
> > [ 1090.606501] CIFS VFS: Received no data, expecting 4
> > [ 1120.575675] CIFS VFS: Received no data, expecting 4
> > [ 1150.544783] CIFS VFS: Received no data, expecting 4
> > [ 1180.513925] CIFS VFS: Received no data, expecting 4
> > [ 1210.483044] CIFS VFS: Received no data, expecting 4
> > [ 1240.452187] CIFS VFS: Received no data, expecting 4
> > [ 1270.421345] CIFS VFS: Received no data, expecting 4
> > [ 1300.390432] CIFS VFS: Received no data, expecting 4
> > [ 1330.359595] CIFS VFS: Received no data, expecting 4
> > [ 1360.328755] CIFS VFS: Received no data, expecting 4
> > [ 1390.283901] CIFS VFS: Received no data, expecting 4
> > [ 1420.249492] CIFS VFS: Received no data, expecting 4
> > [ 1450.218690] CIFS VFS: Received no data, expecting 4
> > [ 1480.187842] CIFS VFS: Received no data, expecting 4
> > [ 1510.156925] CIFS VFS: Received no data, expecting 4
> > [ 1540.126080] CIFS VFS: Received no data, expecting 4
> > [ 1570.095264] CIFS VFS: Received no data, expecting 4
> > [ 1600.064381] CIFS VFS: Received no data, expecting 4
> > [ 1630.033567] CIFS VFS: Received no data, expecting 4
> > [ 1660.002595] CIFS VFS: Received no data, expecting 4
> > [ 1689.971796] CIFS VFS: Received no data, expecting 4
> > [ 1719.940916] CIFS VFS: Received no data, expecting 4
> > [ 1749.910064] CIFS VFS: Received no data, expecting 4
> > [ 1779.879160] CIFS VFS: Received no data, expecting 4
> > [ 1809.848347] CIFS VFS: Received no data, expecting 4
> > [ 1839.817414] CIFS VFS: Received no data, expecting 4
> > [ 1869.786612] CIFS VFS: Received no data, expecting 4
> > [ 1899.755742] CIFS VFS: Received no data, expecting 4
> > [ 1929.724890] CIFS VFS: Received no data, expecting 4
> > [ 1959.694018] CIFS VFS: Received no data, expecting 4
> > [ 1989.663177] CIFS VFS: Received no data, expecting 4
> > [ 2019.632306] CIFS VFS: Received no data, expecting 4
> > [ 2049.601480] CIFS VFS: Received no data, expecting 4
> >
> > Justin.
> >
>
> -Suresh
> --
> To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jeff Layton <jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org>
next prev parent reply other threads:[~2011-09-21 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1109181258480.8689@p34.internal.lan>
[not found] ` <alpine.DEB.2.02.1109181258480.8689-0qmrozcXWo8bm2hyYBkBBg@public.gmane.org>
2011-09-21 11:24 ` 3.1-rc4: CIFS VFS: Received no data, expecting 4 Suresh Jayaraman
[not found] ` <4E79C958.7080702-IBi9RG/b67k@public.gmane.org>
2011-09-21 11:57 ` Jeff Layton [this message]
[not found] ` <20110921075730.74c3b512-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-09-21 11:56 ` Justin Piszcz
[not found] ` <alpine.DEB.2.02.1109210756390.31360-0qmrozcXWo8bm2hyYBkBBg@public.gmane.org>
2011-09-21 13:15 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110921075730.74c3b512@corrin.poochiereds.net \
--to=jlayton-vpemndpepfumzcb2o+c8xq@public.gmane.org \
--cc=jpiszcz-BP4nVm5VUdNhbmWW9KSYcQ@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sjayaraman-IBi9RG/b67k@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox