From: Will Deacon <will@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: CKI Project <cki-project@redhat.com>,
skt-results-master@redhat.com, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org,
Fendy Tjahjadi <ftjahjad@redhat.com>,
Memory Management <mm-qe@redhat.com>,
Jan Stancek <jstancek@redhat.com>,
guro@fb.com, willy@infradead.org, tj@kernel.org,
dennis@kernel.org, linux-mm@kvack.org
Subject: Re: ❌ FAIL: Test report for kernel 5.14.0-rc1 (arm-next, e6f85cbe)
Date: Fri, 16 Jul 2021 11:16:18 +0100 [thread overview]
Message-ID: <20210716101618.GA2946@willie-the-truck> (raw)
In-Reply-To: <20210716100159.GE31920@quack2.suse.cz>
On Fri, Jul 16, 2021 at 12:01:59PM +0200, Jan Kara wrote:
> On Fri 16-07-21 10:03:25, Will Deacon wrote:
> > On Thu, Jul 15, 2021 at 11:55:34PM -0000, CKI Project wrote:
> > > All kernel binaries, config files, and logs are available for download here:
> > >
> > > https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/07/15/337870374
> > >
> > > One or more kernel tests failed:
> > >
> > > aarch64:
> > > 💥 Podman system integration test - as user
> >
> > This is a NULL pointer dereference in the recently introduced
> > cleanup_offline_cgwbs_workfn() function [c22d70a162d3 ("writeback, cgroup:
> > release dying cgwbs by switching attached inodes")]. Adding some of those
> > folks to CC.
>
> Thanks for report! This bug was already reported here [1] and Roman already
> has a tenative fix. Stay tuned :)
Perfect, thanks! I tried searching lkml for "cleanup_offline_cgwbs_workfn"
but didn't think to try fsdevel, so sorry for the duplicate report.
Will
prev parent reply other threads:[~2021-07-16 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cki.552CEC4C85.JGTIJ5O0Q4@redhat.com>
2021-07-16 9:03 ` Will Deacon
2021-07-16 10:01 ` Jan Kara
2021-07-16 10:16 ` Will Deacon [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=20210716101618.GA2946@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=dennis@kernel.org \
--cc=ftjahjad@redhat.com \
--cc=guro@fb.com \
--cc=jack@suse.cz \
--cc=jstancek@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=mm-qe@redhat.com \
--cc=skt-results-master@redhat.com \
--cc=tj@kernel.org \
--cc=willy@infradead.org \
/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