From: Thiago Rafael Becker <firstname.lastname@example.org>
To: "Aurélien Aptel" <email@example.com>
Cc: firstname.lastname@example.org, email@example.com,
Subject: Re: [RFC PATCH] cifs: retry lookup and readdir when EAGAIN is returned.
Date: Mon, 7 Jun 2021 10:57:04 -0300 [thread overview]
Message-ID: <YL4lsBT8Amy4Nh87@nyarly.rlyeh.local> (raw)
On Mon, Jun 07, 2021 at 11:32:46AM +0200, Aurélien Aptel wrote:
> If the user session is deleted trying again will always fail. Are you
> sure this is the reason you get this issue?
It is. We can explicitly delete the user sesssion on windows prior to one
of these calls, which will be replyed with STATUS_USER_SESSION_DELETED.
470 0.0 client → server SMB2 198 Create Request File:
471 0.n server → client SMB2 143 Create Response, Error: STATUS_USER_SESSION_DELETED
Which is converted to EAGAIN with the expectation that someone will
handle it down the stack while the user session is restablished. This
doesn't happen currently, and EAGAIN is leaking to userspace.
For getdents, EAGAIN is unexpected, and most applications don't bother
handling it, including coreutils (ls and stat were used to test this
patch). And for several syscalls that rely on lookup, returning EAGAIN is
unexpected, so we shouldn't leak it.
In our testing, sending the call again handles the problem with no userspace disrruption.
next prev parent reply other threads:[~2021-06-07 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 17:41 [RFC PATCH] cifs: retry lookup and readdir when EAGAIN is returned Thiago Rafael Becker
2021-06-07 9:32 ` Aurélien Aptel
2021-06-07 13:57 ` Thiago Rafael Becker [this message]
2021-06-07 15:27 ` Thiago Rafael Becker
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).