From: Misbah Anjum N <misanjum@linux.ibm.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Ritesh Harjani <riteshh@linux.ibm.com>,
yosry.ahmed@linux.dev, linuxppc-dev@lists.ozlabs.org,
linux-mm@kvack.org, maddy@linux.ibm.com, mpe@ellerman.id.au,
npiggin@gmail.com, christophe.leroy@csgroup.eu,
naveen@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG][powerpc] OOPs: Kernel access of bad area during zram swap write - kswapd0 crash
Date: Mon, 19 May 2025 23:37:13 +0530 [thread overview]
Message-ID: <29cec5ca090a1b833c6a68d103ef9e15@linux.ibm.com> (raw)
In-Reply-To: <6r6hex7p53bsbaje4u7so7tfsz6jemazerzujzraibiah7eq4b@m5vgjaff2cdz>
On 2025-05-07 06:03, Sergey Senozhatsky wrote:
> Hi,
>
> On (25/05/06 11:09), Misbah Anjum N wrote:
>> I am facing this issue even with the latest kernel:
>> 6.15.0-rc4-g5721cf0b9352
>> The suspecting commit is: 44f76413496ec343da0d8292ceecdcabe3e6ec16.
>> The
>> commit introduces zs_obj_write() function.
>> Link:
>> https://github.com/torvalds/linux/commit/44f76413496ec343da0d8292ceecdcabe3e6ec16
>
> Can you try the following fix
> https://lore.kernel.org/linux-mm/20250504110650.2783619-1-senozhatsky@chromium.org
Hi,
Thank you for the patch. I can confirm that it resolves the issue. After
applying it, the kernel panic no longer occurs during memory reclaim
with in my KVM guest testing environment. The Avocado-VT functional
tests now complete successfully.
Patch:
Author: Sergey Senozhatsky <senozhatsky@chromium.org>
Date: Sun May 4 20:00:22 2025 +0900
zsmalloc: don't underflow size calculation in zs_obj_write()
Thank You,
Misbah Anjum N
prev parent reply other threads:[~2025-05-19 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-20 20:41 [BUG][powerpc] OOPs: Kernel access of bad area during zram swap write - kswapd0 crash Misbah Anjum N
2025-04-21 3:49 ` Ritesh Harjani
2025-04-28 5:09 ` Misbah Anjum N
2025-05-06 5:39 ` Misbah Anjum N
2025-05-07 0:33 ` Sergey Senozhatsky
2025-05-19 18:07 ` Misbah Anjum N [this message]
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=29cec5ca090a1b833c6a68d103ef9e15@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 \
--cc=senozhatsky@chromium.org \
--cc=yosry.ahmed@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.