From: "Elliott, Robert (Servers)" <elliott@hpe.com>
To: Phillip Lougher <phillip@squashfs.org.uk>,
Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>,
LKML <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>
Cc: "phillip.lougher@gmail.com" <phillip.lougher@gmail.com>,
Thorsten Leemhuis <regressions@leemhuis.info>
Subject: RE: BUG: in squashfs_xz_uncompress() (Was: RCU stalls in squashfs_readahead())
Date: Fri, 18 Nov 2022 16:51:26 +0000 [thread overview]
Message-ID: <MW5PR84MB1842F7A2DD9A9948A647AC5DAB099@MW5PR84MB1842.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <02877aee-8c05-6534-8a91-94ba366d0276@squashfs.org.uk>
> -----Original Message-----
> From: Phillip Lougher <phillip@squashfs.org.uk>
> Sent: Friday, November 18, 2022 12:11 AM
> To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>; LKML <linux-
> kernel@vger.kernel.org>; Paul E. McKenney <paulmck@kernel.org>
> Cc: phillip.lougher@gmail.com; Thorsten Leemhuis
> <regressions@leemhuis.info>
> Subject: Re: BUG: in squashfs_xz_uncompress() (Was: RCU stalls in
> squashfs_readahead())
>
> On 17/11/2022 23:05, Mirsad Goran Todorovac wrote:
> > Hi,
> >
> > While trying to bisect, I've found another bug that predated the
> > introduction of squashfs_readahead(), but it has
> > a common denominator in squashfs_decompress() and
> squashfs_xz_uncompress().
>
> Wrong, the stall is happening in the XZ decompressor library, which
> is *not* in Squashfs.
>
> This reported stall in the decompressor code is likely a symptom of you
> deliberately thrashing your system. When the system thrashes everything
> starts to happen very slowly, and the system will spend a lot of
> its time doing page I/O, and the CPU will spend a lot of time in
> any CPU intensive code like the XZ decompressor library.
>
> So the fact the stall is being hit here is a symptom and not
> a cause. The decompressor code is likely running slowly due to
> thrashing and waiting on paged-out buffers. This is not indicative
> of any bug, merely a system running slowly due to overload.
>
> As I said, this is not a Squashfs issue, because the code when the
> stall takes place isn't in Squashfs.
>
> The people responsible for the rcu code should have a lot more insight
> about what happens when the system is thrashing, and how this will
> throw up false positives. In this I believe this is an instance of
> perfectly correct code running slowly due to thrashing incorrectly
> being flagged as looping.
>
> CC'ing Paul E. McKenney <paulmck@kernel.org>
>
> Phillip
How big can these readahead sizes be? Should one of the loops include
cond_resched() calls?
next prev parent reply other threads:[~2022-11-18 16:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 19:21 RCU stalls in squashfs_readahead() Mirsad Goran Todorovac
2022-11-17 23:05 ` BUG: in squashfs_xz_uncompress() (Was: RCU stalls in squashfs_readahead()) Mirsad Goran Todorovac
2022-11-17 23:40 ` Mirsad Goran Todorovac
2022-11-18 6:11 ` Phillip Lougher
2022-11-18 15:17 ` Mirsad Goran Todorovac
2022-11-18 15:55 ` Paul E. McKenney
2022-11-20 15:49 ` BUG: BISECTED: " Mirsad Goran Todorovac
2022-11-20 17:50 ` Paul E. McKenney
2022-11-20 18:36 ` Mirsad Goran Todorovac
2022-11-20 19:21 ` Paul E. McKenney
2022-11-21 4:04 ` Mirsad Goran Todorovac
2022-11-22 2:07 ` Paul E. McKenney
2022-11-23 9:14 ` Mirsad Goran Todorovac
2022-11-23 14:44 ` Paul E. McKenney
2022-11-23 16:08 ` Elliott, Robert (Servers)
2022-11-23 19:09 ` Paul E. McKenney
2022-11-24 17:06 ` Mirsad Goran Todorovac
2022-11-24 17:19 ` Paul E. McKenney
2022-11-24 18:04 ` Mirsad Goran Todorovac
2022-11-24 19:32 ` Phillip Lougher
2022-12-06 20:35 ` Mirsad Goran Todorovac
2022-11-24 20:15 ` Paul E. McKenney
2022-11-20 19:33 ` Mirsad Goran Todorovac
2022-11-18 16:51 ` Elliott, Robert (Servers) [this message]
2022-12-20 10:43 ` BUG: " Mirsad Todorovac
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=MW5PR84MB1842F7A2DD9A9948A647AC5DAB099@MW5PR84MB1842.NAMPRD84.PROD.OUTLOOK.COM \
--to=elliott@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=paulmck@kernel.org \
--cc=phillip.lougher@gmail.com \
--cc=phillip@squashfs.org.uk \
--cc=regressions@leemhuis.info \
/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
all inboxes | Powered by JetHome®