mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: linux-erofs@lists.ozlabs.org, xiang@kernel.org, chao@kernel.org,
	huyue2@coolpad.com, jefflexu@linux.alibaba.com
Cc: joneslee@google.com, linux-kernel@vger.kernel.org
Subject: Re: BUG: unable to handle kernel paging request in z_erofs_decompress_queue
Date: Thu, 15 Dec 2022 15:07:46 +0200	[thread overview]
Message-ID: <68bae3be-9a98-83b1-a378-b7c7c12f74c7@linaro.org> (raw)
In-Reply-To: <17c7a0fb-9dc3-6197-358b-894aeb8ee662@linaro.org>



On 15.12.2022 14:58, Tudor Ambarus wrote:
> Hi, Gao, Chao, Yue, Jeffle, all,
> 
> Syzbot reported a bug at [1] that is reproducible in upstream kernel
> since
>    commit 47e4937a4a7c ("erofs: move erofs out of staging")
> 
> and up to (inclusively)
>    commit 2bfab9c0edac ("erofs: record the longest decompressed size in 
> this round")
> 
> The first commit that makes this bug go away is:
>    commit 267f2492c8f7 ("erofs: introduce multi-reference pclusters 
> (fully-referenced)")
> Although, this commit looks like new support and not like an explicit
> bug fix.
> 
> I'd like to fix the lts kernels. I'm happy to try any suggestions or do
> some tests. Please let me know if the bug rings a bell.
> 

There's something else that may help. I enabled CONFIG_EROFS_FS_DEBUG
while at
   commit 2bfab9c0edac ("erofs: record the longest decompressed size in 
this round")
and I got the following: https://termbin.com/4bm8

Cheers,
ta

> [1] 
> https://syzkaller.appspot.com/bug?id=a9b56d324d0de9233ad80633826fac76836d792a

  reply	other threads:[~2022-12-15 13:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 12:58 Tudor Ambarus
2022-12-15 13:07 ` Tudor Ambarus [this message]
2022-12-15 14:24 ` Gao Xiang
2022-12-20 15:42   ` Tudor Ambarus
2022-12-21  2:28     ` Gao Xiang

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=68bae3be-9a98-83b1-a378-b7c7c12f74c7@linaro.org \
    --to=tudor.ambarus@linaro.org \
    --cc=chao@kernel.org \
    --cc=huyue2@coolpad.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=joneslee@google.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiang@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

all inboxes | Powered by JetHome®