From: Miklos Szeredi <miklos@szeredi.hu>
To: michael+lkml@stapelberg.ch
Cc: fuse-devel <fuse-devel@lists.sourceforge.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kyle Sanderson <kyle.leet@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Still a pretty bad time on 5.4.6 with fuse_request_end.
Date: Tue, 11 Feb 2020 11:55:46 +0100 [thread overview]
Message-ID: <CAJfpegv4iL=bW3TXP3F9w1z6-LUox8KiBmw7UBcWE-0jiK0YsA@mail.gmail.com> (raw)
In-Reply-To: <20200209080918.1562823-1-michael+lkml@stapelberg.ch>
On Sun, Feb 9, 2020 at 9:09 AM <michael+lkml@stapelberg.ch> wrote:
>
> From: Michael Stapelberg <michael+lkml@stapelberg.ch>
>
> Hey,
>
> I recently ran into this, too. The symptom for me is that processes using the
> affected FUSE file system hang indefinitely, sync(2) system calls hang
> indefinitely, and even triggering an abort via echo 1 >
> /sys/fs/fuse/connections/*/abort does not get the file system unstuck (there is
> always 1 request still pending). Only removing power will get the machine
> unstuck.
>
> I’m triggering this when building packages for https://distr1.org/, which uses a
> FUSE daemon (written in Go using the jacobsa/fuse package) to provide package
> contents.
>
> I bisected the issue to commit
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2b319d1f6f92a4ced9897678113d176ee16ae85d
>
> With that commit, I run into a kernel oops within ≈1 minute after starting my
> batch build. With the commit before, I can batch build for many minutes without
> issues.
Pretty weird. I'm not seeing how this could change behavior, as the
args->end value is not changed after being initialized, and so moving
the test later should not make a difference.
Could you print out the complete contents of req->args?
Thanks,
Miklos
next prev parent reply other threads:[~2020-02-11 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 1:15 Still a pretty bad time on 5.4.6 with fuse_request_end Kyle Sanderson
2020-01-05 8:08 ` Greg KH
2020-01-16 11:06 ` Miklos Szeredi
2020-02-09 8:09 ` michael+lkml
2020-02-11 10:55 ` Miklos Szeredi [this message]
2020-02-12 7:58 ` Michael Stapelberg
2020-02-12 8:34 ` Miklos Szeredi
2020-02-12 9:38 ` Michael Stapelberg
2020-02-12 19:36 ` Miklos Szeredi
2020-02-13 7:23 ` Michael Stapelberg
2020-03-10 18:07 ` Vivek Goyal
2020-03-06 9:31 Bruno Thomsen
2020-03-09 19:03 ` Greg KH
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='CAJfpegv4iL=bW3TXP3F9w1z6-LUox8KiBmw7UBcWE-0jiK0YsA@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=fuse-devel@lists.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=kyle.leet@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael+lkml@stapelberg.ch \
/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).