From: Vasily Averin <vvs@virtuozzo.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
linux-fsdevel@vger.kernel.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
mszeredi@redhat.com
Subject: Re: [5.8RC4][bugreport]WARNING: CPU: 28 PID: 211236 at fs/fuse/file.c:1684 tree_insert+0xaf/0xc0 [fuse]
Date: Mon, 13 Jul 2020 12:03:45 +0300 [thread overview]
Message-ID: <30a611e6-f445-494e-dab9-d7a5c17c9889@virtuozzo.com> (raw)
In-Reply-To: <CABXGCsO+YH62cjT_pF1RMqKD86Zug4CiWzv6QATe_zhEp3eaeQ@mail.gmail.com>
On 7/13/20 11:02 AM, Mikhail Gavrilov wrote:
> On Mon, 13 Jul 2020 at 12:11, Mikhail Gavrilov
> <mikhail.v.gavrilov@gmail.com> wrote:
>>
>> On Mon, 13 Jul 2020 at 03:28, Mikhail Gavrilov
>> <mikhail.v.gavrilov@gmail.com> wrote:
>>>
>>> Hi folks.
>>> While testing 5.8 RCs I founded that kernel log flooded by the message
>>> "WARNING: CPU: 28 PID: 211236 at fs/fuse/file.c:1684 tree
>>> insert+0xaf/0xc0 [fuse]" when I start podman container.
>>> In kernel 5.7 not has such a problem.
>>
>> Maxim, I suppose you leave `WARN_ON(!wpa->ia.ap.num_pages);` for debug purpose?
>> Now this line is often called when I start the container.
>>
>
> That odd, but I can't send an email to the author of the commit.
> mpatlasov wasn't found at virtuozzo.com.
Reported problem is not fixed yet in 5.8-rc kernels
Please take look at
https://lkml.org/lkml/2020/7/13/265
Thank you,
Vasily Averin
prev parent reply other threads:[~2020-07-13 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 22:28 [5.8RC4][bugreport]WARNING: CPU: 28 PID: 211236 at fs/fuse/file.c:1684 tree_insert+0xaf/0xc0 [fuse] Mikhail Gavrilov
2020-07-13 7:11 ` Mikhail Gavrilov
2020-07-13 8:02 ` Mikhail Gavrilov
2020-07-13 9:03 ` Vasily Averin [this message]
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=30a611e6-f445-494e-dab9-d7a5c17c9889@virtuozzo.com \
--to=vvs@virtuozzo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=mszeredi@redhat.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).