From: Paulo Alcantara <pc@cjr.nz>
To: "Aurélien Aptel" <aaptel@suse.com>,
"Martijn de Gouw" <martijn.de.gouw@prodrive-technologies.com>,
linux-cifs@vger.kernel.org
Subject: Re: Kernel hangs in cifs_reconnect
Date: Tue, 15 Oct 2019 13:27:07 -0300 [thread overview]
Message-ID: <87a7a2ynxg.fsf@cjr.nz> (raw)
In-Reply-To: <871rveaurv.fsf@suse.com>
Aurélien Aptel <aaptel@suse.com> writes:
> Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com> writes:
>> Our Linux VMs reports call traces about processes being stuck.
>> I've attached the full dmesg of one of the call traces below.
>>
>> The machine is running kernel 5.3.1 SMP. All mounts are mounted via the
>> dfs shares on our domain controller and have the following options in fstab:
>> nohandlecache,multiuser,sec=krb5,noperm,user=xxxx,file_mode=0600,dir_mode=0700,vers=3.0
>
> It looks like its DFS related. The DFS cache code takes the reconnect
> mutex and crashes with no chance to give back the mutex, making all
> other process hang while waiting for it.
Yeah, makes sense.
Martijn,
Could you please provide us with some debug logs with the following:
# echo 'module cifs +p' > /sys/kernel/debug/dynamic_debug/control
# echo 'file fs/cifs/* +p' > /sys/kernel/debug/dynamic_debug/control
# echo 1 > /proc/fs/cifs/cifsFYI
# echo 1 > /sys/module/dns_resolver/parameters/debug
Besides, if you could also enable KASAN, that would be great.
Thanks,
Paulo
next prev parent reply other threads:[~2019-10-15 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 15:55 Kernel hangs in cifs_reconnect Martijn de Gouw
2019-10-15 15:33 ` Aurélien Aptel
2019-10-15 16:27 ` Paulo Alcantara [this message]
2019-10-20 8:13 ` Martijn de Gouw
2019-10-29 11:07 ` Martijn de Gouw
2019-10-29 14:49 ` Paulo Alcantara
2019-10-29 18:38 ` Martijn de Gouw
2019-10-30 19:17 ` Martijn de Gouw
2019-10-30 19:33 ` Paulo Alcantara
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=87a7a2ynxg.fsf@cjr.nz \
--to=pc@cjr.nz \
--cc=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=martijn.de.gouw@prodrive-technologies.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;
as well as URLs for NNTP newsgroup(s).