stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laura Abbott <labbott@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Rachel Sibley <rasibley@redhat.com>,
	CKI Project <cki-project@redhat.com>,
	Linux Stable maillist <stable@vger.kernel.org>,
	Memory Management <mm-qe@redhat.com>,
	Jan Stancek <jstancek@redhat.com>,
	LTP Mailing List <ltp@lists.linux.it>
Subject: Re: ❌ FAIL: Stable queue: queue-5.3
Date: Tue, 19 Nov 2019 07:50:56 -0500	[thread overview]
Message-ID: <236c4f8d-a54e-daa6-0896-eca236e23e58@redhat.com> (raw)
In-Reply-To: <20191119124428.GC1975017@kroah.com>

On 11/19/19 7:44 AM, Greg KH wrote:
> On Tue, Nov 19, 2019 at 07:37:09AM -0500, Laura Abbott wrote:
>> On 11/18/19 7:07 PM, Rachel Sibley wrote:
>>>
>>> On 11/18/19 10:00 AM, 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: 116a395b7061 - Linux 5.3.11
>>>>
>>>> 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/293063
>>>>
>>>> One or more kernel tests failed:
>>>>
>>>>       aarch64:
>>>>        ❌ LTP lite
>>>
>>> I see a panic when installing the LTP dependencies
>>>
>>> [  690.625060] Call trace:
>>> [  690.627495]  bfq_find_set_group+0x8c/0xf0
>>> [  690.631491]  bfq_bic_update_cgroup+0xbc/0x218
>>> [  690.635834]  bfq_init_rq+0xac/0x808
>>> [  690.639309]  bfq_insert_request.isra.0+0xe0/0x200
>>> [  690.643999]  bfq_insert_requests+0x68/0x88
>>> [  690.648085]  blk_mq_sched_insert_requests+0x84/0x140
>>> [  690.653036]  blk_mq_flush_plug_list+0x170/0x2b0
>>> [  690.657555]  blk_flush_plug_list+0xec/0x100
>>> [  690.661725]  blk_mq_make_request+0x200/0x5e8
>>> [  690.665982]  generic_make_request+0x94/0x270
>>> [  690.670239]  submit_bio+0x34/0x168
>>> [  690.673712]  xfs_submit_ioend.isra.0+0x9c/0x180 [xfs]
>>> [  690.678798]  xfs_do_writepage+0x234/0x458 [xfs]
>>> [  690.683318]  write_cache_pages+0x1a4/0x3f8
>>> [  690.687442]  xfs_vm_writepages+0x84/0xb8 [xfs]
>>> [  690.691874]  do_writepages+0x3c/0xe0
>>> [  690.695438]  __writeback_single_inode+0x48/0x440
>>> [  690.700042]  writeback_sb_inodes+0x1ec/0x4b0
>>> [  690.704298]  __writeback_inodes_wb+0x50/0xe8
>>> [  690.708555]  wb_writeback+0x264/0x388
>>> [  690.712204]  wb_do_writeback+0x300/0x358
>>> [  690.716113]  wb_workfn+0x80/0x1e0
>>> [  690.719418]  process_one_work+0x1bc/0x3e8
>>> [  690.723414]  worker_thread+0x54/0x440
>>> [  690.727064]  kthread+0x104/0x130
>>> [  690.730281]  ret_from_fork+0x10/0x18
>>> [  690.733847] Code: eb00007f 54000220 b4000040 f8568022 (f9401c42)
>>> [  690.739928] ---[ end trace d3fd392f569e86d3 ]---
>>>
>>> https://artifacts.cki-project.org/pipelines/293063/logs/aarch64_host_2_console.log
>>>
>>
>> This looks like that same issue
>> https://bugzilla.redhat.com/show_bug.cgi?id=1767539
>>
>> I don't think the BFQ fix has been sent to stable yet, or at least
>> it was not in 5.3.11
> 
> Any specific git commit id I should be picking up for this?
> 
> thanks,
> 
> greg k-h
> 

Should be 478de3380c1c ("block, bfq: deschedule empty bfq_queues
not referred by any process") .

Thanks,
Laura


  reply	other threads:[~2019-11-19 12:51 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18 15:00 ❌ FAIL: Stable queue: queue-5.3 CKI Project
     [not found] ` <8e0fa6de-b6b1-23ac-9e77-d425c8d1ba22@redhat.com>
2019-11-19 12:37   ` Laura Abbott
2019-11-19 12:44     ` Greg KH
2019-11-19 12:50       ` Laura Abbott [this message]
2019-11-21 17:53         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2019-11-26  2:00 CKI Project
2019-11-22  1:23 CKI Project
2019-11-11 21:58 CKI Project
2019-11-11 19:57 CKI Project
2019-11-11 15:36 CKI Project
2019-11-11 20:10 ` Rachel Sibley
2019-11-11 20:47   ` Laura Abbott
2019-11-11 12:50 CKI Project
2019-11-11 11:43 CKI Project
2019-11-10 16:12 CKI Project
2019-11-08 23:24 CKI Project
2019-11-08 21:16 CKI Project
2019-11-08 21:55 ` Ondrej Mosnacek
2019-11-08  5:51 CKI Project
2019-11-06 20:56 CKI Project
2019-11-07 10:22 ` Hangbin Liu
2019-11-05  2:51 CKI Project
2019-11-05  1:14 CKI Project
2019-11-05  6:37 ` Greg KH
2019-11-05  8:15   ` Naresh Kamboju
2019-11-04 11:21 CKI Project
2019-10-30 20:12 CKI Project
2019-10-29 20:22 CKI Project
2019-10-29 17:48 CKI Project
2019-10-28  2:44 CKI Project
2019-10-28  2:30 CKI Project
2019-10-28  1:22 CKI Project
2019-10-27 23:47 CKI Project
2019-10-27 14:34 CKI Project
2019-10-27  9:18 CKI Project
2019-10-27  9:08 CKI Project
2019-10-27  9:20 ` Sasha Levin
2019-10-26 22:33 CKI Project
2019-10-27  7:02 ` Naresh Kamboju
2019-10-27  9:32   ` Jan Stancek
2019-10-25 11:25 CKI Project
2019-10-22  2:54 CKI Project
2019-10-16 14:03 CKI Project
2019-10-16 13:56 CKI Project
2019-10-15 22:30 CKI Project
2019-10-15  6:39 CKI Project
2019-10-15  4:49 CKI Project
2019-10-10 13:17 CKI Project
2019-10-10 10:26 CKI Project
2019-10-10 10:51 ` Veronika Kabatova
2019-10-10  6:43 CKI Project
2019-10-09 22:11 CKI Project
2019-10-09 22:44 ` Sasha Levin
2019-10-10  1:09   ` Don Zickus
2019-10-10  6:30     ` Naresh Kamboju
2019-10-16 17:25       ` ? " Jakub Racek
2019-10-08 19:17  " CKI Project
2019-10-08 19:10 CKI Project
2019-10-08 18:03 CKI Project
2019-10-08 18:57 ` Greg KH
2019-10-06  4:57 CKI Project
2019-10-01 19:25 CKI Project
2019-10-01 18:32 CKI Project
2019-10-01 19:19 ` Greg KH

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=236c4f8d-a54e-daa6-0896-eca236e23e58@redhat.com \
    --to=labbott@redhat.com \
    --cc=cki-project@redhat.com \
    --cc=greg@kroah.com \
    --cc=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=mm-qe@redhat.com \
    --cc=rasibley@redhat.com \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).