From: Misbah Anjum N <misanjum@linux.ibm.com>
To: Ritesh Harjani <riteshh@linux.ibm.com>
Cc: christophe.leroy@csgroup.eu, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
maddy@linux.ibm.com, mpe@ellerman.id.au, naveen@kernel.org,
npiggin@gmail.com
Subject: Re: [BUG][powerpc] OOPs: Kernel access of bad area during zram swap write - kswapd0 crash
Date: Mon, 28 Apr 2025 10:39:16 +0530 [thread overview]
Message-ID: <bcec125a551e086911f82cef7bd632fd@linux.ibm.com> (raw)
In-Reply-To: <87ldrujhr5.fsf@gmail.com>
On 2025-04-21 09:19, Ritesh Harjani wrote:
> Looks like the issue is happening on 6.15-rc2. Did git bisect revealed
> a
> faulty commit?
>
> Looks like zsmalloc new object mapping API being called, which was
> merged in rc1? But let's first confirm from git bisect, unless someone
> from linux-mm who knows zsmalloc subsystem better and can point on what
> could be going wrong here.
>
> -ritesh
Hi,
Regarding the issue, I am currently running tests by removing the
suspected faulty commit. Unfortunately, git bisect is not feasible in
this case because recreating the bug requires running the avocado bucket
for approximately two days. Hence, I am resetting the kernel to the
commit prior to: 44f76413496ec343da0d8292ceecdcabe3e6ec16 and manually
running the bucket to come to conclusions.
The commit in question: 44f76413496ec343da0d8292ceecdcabe3e6ec16
introduces zsmalloc - new object mapping API
More information:
https://github.com/torvalds/linux/commit/44f76413496ec343da0d8292ceecdcabe3e6ec16
I will update the upstream bug report with this information after
performing the tests.
Thank you,
Misbah Anjum N
next prev parent reply other threads:[~2025-04-28 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <89bfdedb74416156423d36d28c5b92e9@linux.ibm.com>
2025-04-21 3:49 ` Ritesh Harjani
2025-04-28 5:09 ` Misbah Anjum N [this message]
2025-05-06 5:39 ` Misbah Anjum N
2025-05-07 0:33 ` Sergey Senozhatsky
2025-05-19 18:07 ` Misbah Anjum N
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=bcec125a551e086911f82cef7bd632fd@linux.ibm.com \
--to=misanjum@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=riteshh@linux.ibm.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