From: Scott Mayhew <smayhew@redhat.com>
To: David Howells <dhowells@redhat.com>
Cc: trond.myklebust@hammerspace.com, anna.schumaker@netapp.com,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs: add minor version to nfs_server_key for fscache
Date: Wed, 18 Jul 2018 08:12:16 -0400 [thread overview]
Message-ID: <20180718121216.GK10135@coeurl.usersys.redhat.com> (raw)
In-Reply-To: <9138.1531475067@warthog.procyon.org.uk>
On Fri, 13 Jul 2018, David Howells wrote:
> Scott Mayhew <smayhew@redhat.com> wrote:
>
> > kernel BUG at fs/cachefiles/namei.c:194!
>
> Note that the cachefiles dumps a load of info immediately prior to this BUG()
> which should be included in the description.
>
> Can you also try the four patches at the top of this branch from Kiran Kumar
> Modukuri?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-fixes
>
> The topmost patch removes the BUG() and lets it fall through to the wait. The
> "Fix missing clear of the CACHEFILES_OBJECT_ACTIVE flag" patch fixes one of
> the causes of the BUG.
With v4.18-rc5 plus those four patches, I no longer get the "Unexpected
object collision" message when running cthon (and no oops either,
obviously).
-Scott
>
> David
next prev parent reply other threads:[~2018-07-18 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 12:22 [PATCH] nfs: add minor version to nfs_server_key for fscache Scott Mayhew
2018-07-11 14:51 ` Benjamin Coddington
2018-07-11 16:24 ` Scott Mayhew
2018-07-11 16:48 ` Trond Myklebust
2018-07-12 12:25 ` Scott Mayhew
2018-07-25 10:07 ` David Howells
2018-07-13 9:44 ` David Howells
2018-07-18 12:12 ` Scott Mayhew [this message]
2018-07-18 20:56 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2020-02-24 21:29 Dave Wysochanski
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=20180718121216.GK10135@coeurl.usersys.redhat.com \
--to=smayhew@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=dhowells@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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