From: Matthew Wilcox <willy@infradead.org>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
kernel test robot <oliver.sang@intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-perf-users@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [linus:master] [mm/mmap] 0503ea8f5b: kernel_BUG_at_mm/filemap.c
Date: Mon, 27 Feb 2023 03:52:12 +0000 [thread overview]
Message-ID: <Y/wo7H+ZZzFoEqvk@casper.infradead.org> (raw)
In-Reply-To: <20230227031756.v57rhicna3tjbavw@revolver>
On Sun, Feb 26, 2023 at 10:17:56PM -0500, Liam R. Howlett wrote:
> Are you sure about this bisection? I'm not saying it isn't my fault or
> looking to blame others, but I suspect we are indeed looking at the
> wrong commit here.
I concur. Looking at the backtrace, I think it's more likely to be
a pagecache, swapcache or shmfs issue. I'll look more in the morning.
> > bin/lkp qemu -k <bzImage> -m modules.cgz job-script # job-script is attached in this email
> >
> > # if come across any failure that blocks the test,
> > # please remove ~/.lkp and /lkp dir to run from a clean state.
> >
>
> This does not work for me. Since my last use of lkp it seems something
> was changed and now -watchdog is not recognized by my qemu and so my
> attempts to reproduce this are failing. Is there a way to avoid using
> the -watchdog flag? Running the command by hand fails as it seems some
> files are removed on exit?
https://www.qemu.org/docs/master/about/removed-features.html
-watchdog (since 7.2)
Use -device instead.
(I have no idea what this means, but maybe it's a clue?)
next prev parent reply other threads:[~2023-02-27 3:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202302252122.38b2139-oliver.sang@intel.com>
2023-02-27 3:17 ` [linus:master] [mm/mmap] 0503ea8f5b: kernel_BUG_at_mm/filemap.c Liam R. Howlett
2023-02-27 3:52 ` Matthew Wilcox [this message]
2023-03-01 7:31 ` Oliver Sang
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=Y/wo7H+ZZzFoEqvk@casper.infradead.org \
--to=willy@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.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).