linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Joakim Tjernlund (Nokia)" <joakim.tjernlund@nokia.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Phillip Lougher <phillip@squashfs.org.uk>
Subject: Re: squashfs can starve/block apps
Date: Thu, 26 Jun 2025 14:27:27 +0000	[thread overview]
Message-ID: <88b54d9a1562393526abc4556a6105ef1aca7ace.camel@nokia.com> (raw)
In-Reply-To: <bd03e4e1d56d67644b60b2a58e092a0e3fdcff57.camel@nokia.com>

On Thu, 2025-06-26 at 10:09 +0200, Joakim Tjernlund wrote:
> We have an app running on a squashfs RFS(XZ compressed) and a appfs also on squashfs.
> Whenever we validate an SW update image(stream a image.xz, uncompress it and on to /dev/null), 
> the apps are starved/blocked and make almost no progress, system time in top goes up to 99+%
> and the console also becomes unresponsive.
> 
> This feels like kernel is stuck/busy in a loop and does not let apps execute.
> 
> Kernel 5.15.185
> 
> Any ideas/pointers ?
> 
>  Jocke

This will reproduce the stuck behaviour we see:
 > cd /tmp (/tmp is an tmpfs)
 > wget https://fullImage.xz

So just downloading it to tmpfs will confuse squashfs, seems to
me that squashfs somehow see the xz compressed pages in page cache/VFS and
tried to do something with them.

kernel 51.15.185 (aarch64)
user space: ARM 32 bit with thumb

  reply	other threads:[~2025-06-26 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26  8:09 squashfs can starve/block apps Joakim Tjernlund (Nokia)
2025-06-26 14:27 ` Joakim Tjernlund (Nokia) [this message]
2025-07-04 19:51   ` Phillip Lougher
2025-07-06  9:46     ` Joakim Tjernlund (Nokia)

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=88b54d9a1562393526abc4556a6105ef1aca7ace.camel@nokia.com \
    --to=joakim.tjernlund@nokia.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=phillip@squashfs.org.uk \
    /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).