From: Sasha Levin <sashal@kernel.org>
To: Jan Stancek <jstancek@redhat.com>
Cc: Greg KH <greg@kroah.com>, CKI Project <cki-project@redhat.com>,
Linux Stable maillist <stable@vger.kernel.org>,
Memory Management <mm-qe@redhat.com>,
Xiong Zhou <xzhou@redhat.com>
Subject: Re: ❌ FAIL: Stable queue: queue-5.2
Date: Fri, 23 Aug 2019 11:38:05 -0400 [thread overview]
Message-ID: <20190823153805.GD1581@sasha-vm> (raw)
In-Reply-To: <900819847.7915389.1566543455477.JavaMail.zimbra@redhat.com>
On Fri, Aug 23, 2019 at 02:57:35AM -0400, Jan Stancek wrote:
>
>
>----- Original Message -----
>> On Thu, Aug 22, 2019 at 06:48:50PM -0400, CKI Project wrote:
>> >
>> > Hello,
>> >
>> > We ran automated tests on a patchset that was proposed for merging into
>> > this
>> > kernel tree. The patches were applied to:
>> >
>> > Kernel repo:
>> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
>> > Commit: aad39e30fb9e - Linux 5.2.9
>> >
>> > The results of these automated tests are provided below.
>> >
>> > Overall result: FAILED (see details below)
>> > Merge: OK
>> > Compile: OK
>> > Tests: FAILED
>> >
>> > All kernel binaries, config files, and logs are available for download
>> > here:
>> >
>> > https://artifacts.cki-project.org/pipelines/116984
>> >
>> >
>> >
>> > One or more kernel tests failed:
>> >
>> > aarch64:
>> > ❌ LTP lite
>> > ❌ Loopdev Sanity
>>
>> Odd, what suddenly broke? No new patches had been added to the queue
>> since Tuesday, except I removed a single patch. Removing a patch
>> shouldn't break anything, right?
>
>It's a race:
> [ 1289.578972] LTP: starting mtest06 ( mmap1)
> ...
> [ 1455.794564] kernel BUG at mm/filemap.c:171!
>
>Here's a verbose description:
> https://lore.kernel.org/lkml/50b8914e20d1d62bb2dee42d342836c2c16ebee7.1563438048.git.jstancek@redhat.com/
>
>Final (less verbose) patch:
> e1b98fa31664 ("locking/rwsem: Add missing ACQUIRE to read_slowpath exit when queue is empty")
>
>Code review found also this issue, which is theoretical and very unlikely, but it's a small patch:
> 99143f82a255 ("lcoking/rwsem: Add missing ACQUIRE to read_slowpath sleep loop")
Okay, so this is not a new regression in 5.2 but rather something that
we just ended up hitting now.
We can queue up the fixes for the next release.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-08-23 15:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 22:48 ❌ FAIL: Stable queue: queue-5.2 CKI Project
2019-08-22 23:37 ` Greg KH
2019-08-23 6:57 ` Jan Stancek
2019-08-23 15:38 ` Sasha Levin [this message]
2019-08-23 2:19 ` ? " Murphy Zhou
-- strict thread matches above, loose matches on Subject: below --
2019-09-19 12:42 ❌ " CKI Project
2019-09-19 12:57 ` Greg KH
2019-09-07 11:48 CKI Project
2019-09-04 5:31 CKI Project
2019-09-04 21:40 ` Rachel Sibley
2019-08-30 23:41 CKI Project
2019-08-28 12:36 CKI Project
2019-09-10 8:19 ` Hangbin Liu
2019-09-10 8:58 ` Greg KH
2019-09-10 9:30 ` Hangbin Liu
2019-09-10 9:40 ` Hangbin Liu
2019-09-10 10:52 ` Sasha Levin
2019-08-27 10:54 CKI Project
2019-08-26 22:06 CKI Project
2019-08-27 14:58 ` Rachel Sibley
2019-08-26 20:33 CKI Project
2019-08-26 21:00 ` Major Hayden
2019-08-25 14:37 CKI Project
2019-08-25 14:41 ` Greg KH
2019-08-26 8:23 ` Nikolai Kondrashov
2019-08-26 8:33 ` Greg KH
2019-08-26 9:13 ` Nikolai Kondrashov
2019-08-26 9:40 ` Nikolai Kondrashov
2019-08-26 11:12 ` Nikolai Kondrashov
2019-08-26 11:39 ` Nikolai Kondrashov
2019-08-26 13:33 ` Sasha Levin
2019-08-27 13:10 ` Nikolai Kondrashov
2019-08-18 21:09 CKI Project
2019-08-18 14:27 CKI Project
2019-08-18 14:05 CKI Project
2019-08-18 14:20 ` Greg KH
2019-08-18 12:00 CKI Project
2019-08-18 16:59 ` Ondrej Mosnacek
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=20190823153805.GD1581@sasha-vm \
--to=sashal@kernel.org \
--cc=cki-project@redhat.com \
--cc=greg@kroah.com \
--cc=jstancek@redhat.com \
--cc=mm-qe@redhat.com \
--cc=stable@vger.kernel.org \
--cc=xzhou@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).