From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: miklos@szeredi.hu, michael+lkml@stapelberg.ch
Cc: fuse-devel@lists.sourceforge.net,
Greg KH <gregkh@linuxfoundation.org>,
kyle.leet@gmail.com, linux-fsdevel@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
Bruno Thomsen <bth@kamstrup.com>
Subject: Re: Still a pretty bad time on 5.4.6 with fuse_request_end.
Date: Fri, 6 Mar 2020 10:31:42 +0100 [thread overview]
Message-ID: <CAH+2xPBuLsVjwStj4hQHDEbogKW+mXd2p66DG9X2F8nW+doyHw@mail.gmail.com> (raw)
Hi,
First of all, sorry for the incorrect reply as I was not subscribed to
the mailing list.
A colleague and I have tested Miklos patch[1] on top of Fedora 31
5.5.7 kernel and it fixes a kernel oops[2] when using rootless
containers in Podman. Fix has been running for a few days now,
and the issue was normally reproducible within a few minutes.
Tested-by: Bruno Thomsen <bruno.thomsen@gmail.com>
/Bruno
[1] https://lore.kernel.org/linux-fsdevel/CAJfpegvBguKcNZk-p7sAtSuNH_7HfdCyYvo8Wh7X6P=hT=kPrA@mail.gmail.com/
[2] Oops when running podman workload.
kernel: BUG: kernel NULL pointer dereference, address: 0000000000000001
kernel: #PF: supervisor instruction fetch in kernel mode
kernel: #PF: error_code(0x0010) - not-present page
kernel: PGD 8000000e4cd85067 P4D 8000000e4cd85067 PUD e4cd80067 PMD 0
kernel: Oops: 0010 [#1] SMP PTI
kernel: CPU: 27 PID: 3422 Comm: fuse-overlayfs Not tainted
5.5.5-200.fc31.x86_64 #1
kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraproject.org-3.fc31
04/01/2014
kernel: RIP: 0010:0x1
kernel: Code: Bad RIP value.
kernel: RSP: 0018:ffffaa0d4196fc30 EFLAGS: 00010202
kernel: RAX: 0000000000000001 RBX: ffff8b5f344c2250 RCX: 0000000000000000
kernel: RDX: 0000000000000000 RSI: ffffaa0d4932fbb8 RDI: ffff8b65ac586800
kernel: RBP: ffff8b5f344c2240 R08: ffff8b5f344c22a0 R09: ffffaa0d4196fbd0
kernel: R10: ffff8b65a5c71888 R11: 0000000000000001 R12: ffff8b65ac586800
kernel: R13: 0000000000000001 R14: ffff8b65ab535dc0 R15: ffff8b5f344c2240
kernel: FS: 00007fb4239a7b80(0000) GS:ffff8b65b98c0000(0000)
knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: ffffffffffffffd7 CR3: 0000000e4cd38004 CR4: 0000000000360ee0
kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
kernel: Call Trace:
kernel: ? fuse_request_end+0xbc/0x1f0 [fuse]
kernel: ? fuse_dev_do_write+0x25e/0xe70 [fuse]
kernel: ? lookup_fast+0xca/0x280
kernel: ? fuse_dev_write+0x53/0x90 [fuse]
kernel: ? do_iter_readv_writev+0x158/0x1d0
kernel: ? do_iter_write+0x7d/0x190
kernel: ? vfs_writev+0xa6/0xf0
kernel: ? _copy_to_user+0x28/0x30
kernel: ? readlink_copy+0x5a/0x80
kernel: ? do_writev+0x6b/0x110
kernel: ? do_syscall_64+0x5b/0x1c0
kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
kernel: Modules linked in: tun ip6t_REJECT nf_reject_ipv6
ip6t_rpfilter ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat
ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_>
kernel: CR2: 0000000000000001
next reply other threads:[~2020-03-06 9:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 9:31 Bruno Thomsen [this message]
2020-03-09 19:03 ` Still a pretty bad time on 5.4.6 with fuse_request_end Greg KH
-- strict thread matches above, loose matches on Subject: below --
2020-02-22 19:29 Kyle Sanderson
2020-02-23 9:58 ` Greg KH
2020-01-05 1:15 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
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
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=CAH+2xPBuLsVjwStj4hQHDEbogKW+mXd2p66DG9X2F8nW+doyHw@mail.gmail.com \
--to=bruno.thomsen@gmail.com \
--cc=bth@kamstrup.com \
--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 \
--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 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).