From: Minchan Kim <minchan@kernel.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>,
umgwanakikbuti@gmail.com, bigeasy@linutronix.de
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>,
regressions@lists.linux.dev, Jens Axboe <axboe@kernel.dk>,
Nitin Gupta <ngupta@vflare.org>
Subject: Re: qemu-arm: zram: mkfs.ext4 : Unable to handle kernel NULL pointer dereference at virtual address 00000140
Date: Mon, 13 Jun 2022 09:49:03 -0700 [thread overview]
Message-ID: <Yqdqfz4Ycbg33k1R@google.com> (raw)
In-Reply-To: <YqbtH9F47dkZghJ7@google.com>
On Mon, Jun 13, 2022 at 04:54:07PM +0900, Sergey Senozhatsky wrote:
> Hello,
>
> On (22/06/12 20:56), Naresh Kamboju wrote:
> >
> > I have tested this patch and the reported issue got resolved [1].
> >
>
> Many thanks for the tests.
>
> Quite honestly I was hoping that the patch would not help :) Well, ok,
> we now know that it's mapping area lock and the lockdep part of its
> memory is zero-ed out. The question is - "why?" It really should not
> be zeroed out.
Ccing Mike and Sebastian who are author/expert of the culprit patch
Naresh found zsmalloc crashed on the testing [1] and confirmed
that Sergey's patch[2] fixed the problem.
However, I don't understand why we need reinit the local_lock
on cpu_up handler[3].
Could you guys shed some light?
[1] https://lore.kernel.org/all/CA+G9fYtVOfWWpx96fa3zzKzBPKiNu1w3FOD4j++G8MOG3Vs0EA@mail.gmail.com/
[2] https://lore.kernel.org/all/YqBRZcsfrRMZXMCC@google.com/
[3] https://lore.kernel.org/all/YqEKapKLBgKEXGBg@google.com/
next prev parent reply other threads:[~2022-06-13 19:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 8:49 qemu-arm: zram: mkfs.ext4 : Unable to handle kernel NULL pointer dereference at virtual address 00000140 Naresh Kamboju
2022-06-06 17:36 ` Minchan Kim
2022-06-07 1:21 ` Naresh Kamboju
2022-06-07 23:52 ` Minchan Kim
2022-06-08 2:39 ` Sergey Senozhatsky
2022-06-08 2:42 ` Sergey Senozhatsky
2022-06-08 2:45 ` Sergey Senozhatsky
2022-06-08 7:36 ` Sergey Senozhatsky
2022-06-12 15:26 ` Naresh Kamboju
2022-06-13 7:54 ` Sergey Senozhatsky
2022-06-13 16:49 ` Minchan Kim [this message]
2022-06-14 3:19 ` Sergey Senozhatsky
2022-06-15 16:47 ` Minchan Kim
2022-06-08 20:45 ` Minchan Kim
2022-06-09 11:02 ` Sergey Senozhatsky
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=Yqdqfz4Ycbg33k1R@google.com \
--to=minchan@kernel.org \
--cc=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=ngupta@vflare.org \
--cc=regressions@lists.linux.dev \
--cc=senozhatsky@chromium.org \
--cc=umgwanakikbuti@gmail.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