From: Patrick Noffke <patrick-0qqNeQ6W4hOzQB+pC5nmwQ@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: hung system with cifsd, cannot reduce timeout
Date: Tue, 10 Dec 2013 09:15:41 -0600 [thread overview]
Message-ID: <3540393.5GuVZWBWRs@dingofarm.qg.com> (raw)
In-Reply-To: <1774674.CzhmRQMMgZ-J5+zLgb4AZ5BQzcUTsrH4w@public.gmane.org>
On Friday, December 06, 2013 09:50:27 AM Patrick Noffke wrote:
>
>
> It seems like the "Getting info on" log message is missing a filename. Would
> this explain why it's hung until the server sends a RST?
>
> There are also logs like the following before the cable is reattached:
> fs/cifs/misc.c: Null buffer passed to cifs_small_buf_release
>
In inode.c, in the cifs_revalidate_dentry_attr function, if I add a check for an empty full_path (returning -ENOENT if empty), then the system recovers much faster, but my process gets an error opening the file it was trying to open when the cable was disconnected. I noticed cifs logs following trying to call cifs_revalidate_dentry_attr with the last file path, but there is a NULL inode for several such calls.
I added this right after the check for a NULL full_path:
if (0 != strcmp(full_path, "")) {
cFYI(1, "Got empty full_path");
rc = -ENOENT;
goto out;
}
I don't propose this as a patch -- I'm just curious if I'm on the right track. Could I return something else, or is there some other way to help the file system recover faster?
Thanks,
Patrick
next prev parent reply other threads:[~2013-12-10 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 21:03 hung system with cifsd, cannot reduce timeout Patrick Noffke
[not found] ` <52A0EA24.9000600-0qqNeQ6W4hOzQB+pC5nmwQ@public.gmane.org>
2013-12-05 21:36 ` Patrick Noffke
[not found] ` <52A0F1CB.5060709-0qqNeQ6W4hOzQB+pC5nmwQ@public.gmane.org>
2013-12-06 15:50 ` Patrick Noffke
[not found] ` <1774674.CzhmRQMMgZ-J5+zLgb4AZ5BQzcUTsrH4w@public.gmane.org>
2013-12-10 15:15 ` Patrick Noffke [this message]
[not found] ` <3540393.5GuVZWBWRs-J5+zLgb4AZ5BQzcUTsrH4w@public.gmane.org>
2013-12-14 11:50 ` Jeff Layton
2013-12-31 22:43 ` ISHIKAWA,Chiaki
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=3540393.5GuVZWBWRs@dingofarm.qg.com \
--to=patrick-0qqneq6w4hozqb+pc5nmwq@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@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