From: "Aurélien Aptel" <aaptel@suse.com>
To: Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>,
Steve French <smfrench@gmail.com>
Cc: Pavel Shilovsky <piastryyy@gmail.com>,
linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: Many processes end up in uninterruptible sleep accessing cifs mounts
Date: Mon, 08 Jul 2019 13:06:52 +0200 [thread overview]
Message-ID: <875zocwzsj.fsf@suse.com> (raw)
In-Reply-To: <49b1529a-6d0e-99cc-112c-fa226ddcab1a@prodrive-technologies.com>
Martijn, can you give a try to the PATCH (v2) I sent?
I wrote it on top of the 4.20 stable tree. I understand the process to
apply compile and install is not the easiest one but it would be
extremely helpful since you can reproduce the issue.
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2019-07-08 11:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 18:12 Many processes end up in uninterruptible sleep accessing cifs mounts Martijn de Gouw
2019-07-03 19:17 ` Aurélien Aptel
2019-07-03 19:24 ` Steve French
[not found] ` <1fc4f6d0-6cdc-69a5-4359-23484d6bdfc9@prodrive-technologies.com>
2019-07-04 11:22 ` Aurélien Aptel
2019-07-04 13:36 ` Martijn de Gouw
2019-07-04 21:34 ` Pavel Shilovsky
2019-07-06 11:11 ` Martijn de Gouw
2019-07-06 13:05 ` Steve French
2019-07-06 16:40 ` Pavel Shilovsky
2019-07-09 8:48 ` Martijn de Gouw
2019-07-15 23:40 ` Pavel Shilovsky
2019-08-07 7:34 ` Martijn de Gouw
2019-07-08 9:04 ` Martijn de Gouw
2019-07-08 11:06 ` Aurélien Aptel [this message]
2019-07-08 13:18 ` Martijn de Gouw
2019-07-04 21:08 ` 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=875zocwzsj.fsf@suse.com \
--to=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=martijn.de.gouw@prodrive-technologies.com \
--cc=piastryyy@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;
as well as URLs for NNTP newsgroup(s).