linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Wettenhall <james.wettenhall@monash.edu>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: Steve French <smfrench@gmail.com>, CIFS <linux-cifs@vger.kernel.org>
Subject: Re: Frequent reconnections / session startups?
Date: Wed, 4 Sep 2019 16:46:27 +1000	[thread overview]
Message-ID: <CAE78Er_ea5mtp-6VxyNPzCSDuPym7cXcD3=Udcpv=jGo80XhZg@mail.gmail.com> (raw)
In-Reply-To: <87pnkh7jh2.fsf@suse.com>

Hi Aurélien,

The VMs become completely unresponsive, so we can't run commands in a
separate shell.

I've included a stack trace below.

I'm considering trying the cache=loose mount option.

Cheers,
James

Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.616360] INFO: task
dockerd:786 blocked for more than 120 seconds.
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.621073]       Not
tainted 5.0.0-25-generic #26~18.04.1-Ubuntu
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.625436] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629464] dockerd
D    0   786      1 0x00000000
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629467] Call Trace:
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629477]  __schedule+0x2bd/0x850
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629482]  ?
__switch_to_asm+0x35/0x70
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629484]  schedule+0x2c/0x70
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629485]
schedule_preempt_disabled+0xe/0x10
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629487]
__mutex_lock.isra.9+0x183/0x4e0
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629488]  ?
schedule_timeout+0x171/0x360
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629490]
__mutex_lock_slowpath+0x13/0x20
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629491]  ?
__mutex_lock_slowpath+0x13/0x20
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629492]  mutex_lock+0x2f/0x40
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629528]
smb2_reconnect+0x106/0x7f0 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629531]  ? __switch_to+0x123/0x4e0
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629533]  ?
__switch_to_asm+0x35/0x70
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629537]  ?
__switch_to_asm+0x41/0x70
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629540]  ? wait_woken+0x80/0x80
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629556]
smb2_plain_req_init+0x34/0x270 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629577]
SMB2_open_init+0x6d/0x730 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629595]
SMB2_open+0x148/0x4f0 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629609]  ?
SMB2_open+0x148/0x4f0 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629624]
open_shroot+0x16c/0x210 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629637]  ?
open_shroot+0x16c/0x210 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629654]
smb2_query_path_info+0x11c/0x1b0 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629656]  ? _cond_resched+0x19/0x40
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629660]  ?
kmem_cache_alloc_trace+0x151/0x1c0
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629673]
cifs_get_inode_info+0x3e3/0xb70 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629685]  ?
build_path_from_dentry_optional_prefix+0x103/0x430 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629699]
cifs_revalidate_dentry_attr+0xe9/0x3d0 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629712]
cifs_getattr+0x5d/0x1a0 [cifs]
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629715]  ?
common_perm_cond+0x4c/0x70
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629719]
vfs_getattr_nosec+0x73/0x90
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629720]  vfs_getattr+0x36/0x40
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629721]  vfs_statx+0x8d/0xe0
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629723]
__do_sys_newlstat+0x3d/0x70
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629725]
__x64_sys_newlstat+0x16/0x20
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629729]  do_syscall_64+0x5a/0x120
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629731]
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629734] RIP: 0033:0x55fd5a4b1e40
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629739] Code: Bad RIP value.
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629741] RSP:
002b:000000c421af6948 EFLAGS: 00000212 ORIG_RAX: 0000000000000006
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629742] RAX:
ffffffffffffffda RBX: 0000000000000000 RCX: 000055fd5a4b1e40
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629743] RDX:
0000000000000000 RSI: 000000c421491488 RDI: 000000c4227a4060
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629743] RBP:
000000c421af69b0 R08: 0000000000000000 R09: 0000000000000000
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629744] R10:
0000000000000000 R11: 0000000000000212 R12: ffffffffffffffff
Sep  4 13:36:36 prod-worker-1a kernel: [ 3384.629745] R13:
0000000000000002 R14: 0000000000000001 R15: 0000000000000055

  reply	other threads:[~2019-09-04  6:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26  6:55 Frequent reconnections / session startups? James Wettenhall
2019-08-26 14:55 ` Steve French
2019-08-28  1:50   ` James Wettenhall
2019-09-02  0:23   ` James Wettenhall
2019-09-03 10:38     ` Aurélien Aptel
2019-09-04  6:46       ` James Wettenhall [this message]
2019-09-13 23:47         ` Pavel Shilovsky
     [not found]           ` <CAE78Er97k7O-GDGdMtp0qXtQ-q-1nS_d1AE6HHH+Kz6PV_G2uQ@mail.gmail.com>
2019-09-18  5:23             ` James Wettenhall
2019-09-18  6:49               ` ronnie sahlberg
2019-09-18 17:58                 ` Pavel Shilovsky

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='CAE78Er_ea5mtp-6VxyNPzCSDuPym7cXcD3=Udcpv=jGo80XhZg@mail.gmail.com' \
    --to=james.wettenhall@monash.edu \
    --cc=aaptel@suse.com \
    --cc=linux-cifs@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).