From: Greg KH <gregkh@linuxfoundation.org>
To: Kyle Sanderson <kyle.leet@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, miklos@szeredi.hu,
Linux-Kernal <linux-kernel@vger.kernel.org>,
fuse-devel@lists.sourceforge.net
Subject: Re: Still a pretty bad time on 5.4.6 with fuse_request_end.
Date: Sun, 5 Jan 2020 09:08:08 +0100 [thread overview]
Message-ID: <20200105080808.GA1667342@kroah.com> (raw)
In-Reply-To: <CACsaVZLApLO=dNCU07ZjMx4qA8dv1=OA7n31uD9GzHkSFCm8oA@mail.gmail.com>
On Sat, Jan 04, 2020 at 05:15:30PM -0800, Kyle Sanderson wrote:
> [400280.179731] BUG: unable to handle page fault for address: 0000000044000000
> [400280.179842] #PF: supervisor instruction fetch in kernel mode
> [400280.179938] #PF: error_code(0x0010) - not-present page
> [400280.180032] PGD 0 P4D 0
> [400280.180125] Oops: 0010 [#1] PREEMPT SMP NOPTI
> [400280.180221] CPU: 5 PID: 6894 Comm: mergerfs Not tainted 5.4.6-gentoo #1
"still"?
When did this show up? What were you doing to cause the issue? Can you
run 'git bisect' to find the problem commit? When/where did you report
this problem in the past?
thanks,
greg k-h
next prev parent reply other threads:[~2020-01-05 8:08 UTC|newest]
Thread overview: 15+ 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 [this message]
2020-01-16 11:06 ` Miklos Szeredi
2020-02-09 8:09 ` michael+lkml
2020-02-11 10:55 ` Miklos Szeredi
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
-- strict thread matches above, loose matches on Subject: below --
2020-02-22 19:29 Kyle Sanderson
2020-02-23 9:58 ` Greg KH
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=20200105080808.GA1667342@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=kyle.leet@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.