From: David Howells <dhowells@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: dhowells@redhat.com, Rohith Surabattula <rohiths.msft@gmail.com>,
Steve French <smfrench@gmail.com>,
Shyam Prasad N <nspmangalore@gmail.com>,
ronnie sahlberg <ronniesahlberg@gmail.com>,
Paulo Alcantara <pc@cjr.nz>,
jlayton@kernel.org, linux-cifs@vger.kernel.org
Subject: Re: cifs conversion to netfslib
Date: Thu, 17 Mar 2022 16:16:50 +0000 [thread overview]
Message-ID: <170115.1647533810@warthog.procyon.org.uk> (raw)
In-Reply-To: <4085703.1647475640@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> wrote:
> I am seeing the occasional:
>
> CIFS: trying to dequeue a deleted mid
>
> but I haven't managed to work out how I get to that yet.
That turned out to be due to EFAULT occurring in sock_recvmsg() called from
cifs_readv_from_socket() because it was handed an iovec-class iov_iter. It
went through:
if (length <= 0) {
cifs_dbg(FYI, "Received no data or error: %d\n", length);
cifs_reconnect(server, false);
return -ECONNABORTED;
}
which called cifs_abort_connection() which forcibly marked the MIDs as
deleted. However, they got dequeued later which triggered the message.
Telling netfs's DIO read to turn it into a bvec-class iov_iter instead stopped
that happening, but it's may be a latent problem.
I also found the causes of the occasional "server overflowed SMB3 credits"
messages that I've been seeing:
Firstly, the data read path was returning credits both when freeing the
subrequest and at the end of smb2_readv_callback(). I made the former
conditional on not doing the latter.
Secondly, cifs_write_back_from_locked_page() was returning credits, even if
->async_writev() was successful. I made that only do it on error.
And now it gets through generic/013 for me.
David
next prev parent reply other threads:[~2022-03-17 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 8:19 cifs conversion to netfslib David Howells
2022-03-11 8:25 ` David Howells
2022-03-15 3:50 ` Rohith Surabattula
2022-03-15 9:54 ` Rohith Surabattula
2022-03-17 0:07 ` David Howells
2022-03-17 16:16 ` David Howells [this message]
2022-03-18 0:21 ` David Howells
2022-03-18 2:52 ` Steve French
2022-03-21 10:19 ` Rohith Surabattula
2022-03-21 17:18 ` David Howells
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=170115.1647533810@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=pc@cjr.nz \
--cc=rohiths.msft@gmail.com \
--cc=ronniesahlberg@gmail.com \
--cc=smfrench@gmail.com \
/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