All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	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: Thu, 9 Jun 2022 20:02:41 +0900	[thread overview]
Message-ID: <YqHTUdeZ8H0Lnf8E@google.com> (raw)
In-Reply-To: <YqEKapKLBgKEXGBg@google.com>

On (22/06/08 13:45), Minchan Kim wrote:
> 
> I am trying to understand the problem. AFAIK, the mapping_area was
> static allocation per cpu so in zs_cpu_down, we never free the
> mapping_area itself. Then, why do we need to reinitialize the local
> lock again?

Well... Something zero-s out that memory. NULL deref in strcmp() in
lockdep points at NULL ->name. So I'm merely testing my theories here.
If it's not area lock then it's pool->migrate_lock?

WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	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: Thu, 9 Jun 2022 20:02:41 +0900	[thread overview]
Message-ID: <YqHTUdeZ8H0Lnf8E@google.com> (raw)
In-Reply-To: <YqEKapKLBgKEXGBg@google.com>

On (22/06/08 13:45), Minchan Kim wrote:
> 
> I am trying to understand the problem. AFAIK, the mapping_area was
> static allocation per cpu so in zs_cpu_down, we never free the
> mapping_area itself. Then, why do we need to reinitialize the local
> lock again?

Well... Something zero-s out that memory. NULL deref in strcmp() in
lockdep points at NULL ->name. So I'm merely testing my theories here.
If it's not area lock then it's pool->migrate_lock?

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-06-09 11:02 UTC|newest]

Thread overview: 30+ 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-02  8:49 ` Naresh Kamboju
2022-06-06 17:36 ` Minchan Kim
2022-06-06 17:36   ` Minchan Kim
2022-06-07  1:21   ` Naresh Kamboju
2022-06-07  1:21     ` Naresh Kamboju
2022-06-07 23:52     ` Minchan Kim
2022-06-07 23:52       ` Minchan Kim
2022-06-08  2:39       ` Sergey Senozhatsky
2022-06-08  2:39         ` Sergey Senozhatsky
2022-06-08  2:42         ` Sergey Senozhatsky
2022-06-08  2:42           ` Sergey Senozhatsky
2022-06-08  2:45           ` Sergey Senozhatsky
2022-06-08  2:45             ` Sergey Senozhatsky
2022-06-08  7:36             ` Sergey Senozhatsky
2022-06-08  7:36               ` Sergey Senozhatsky
2022-06-12 15:26               ` Naresh Kamboju
2022-06-12 15:26                 ` Naresh Kamboju
2022-06-13  7:54                 ` Sergey Senozhatsky
2022-06-13  7:54                   ` Sergey Senozhatsky
2022-06-13 16:49                   ` Minchan Kim
2022-06-13 16:49                     ` Minchan Kim
2022-06-14  3:19                     ` Sergey Senozhatsky
2022-06-14  3:19                       ` Sergey Senozhatsky
2022-06-15 16:47                       ` Minchan Kim
2022-06-15 16:47                         ` Minchan Kim
2022-06-08 20:45           ` Minchan Kim
2022-06-08 20:45             ` Minchan Kim
2022-06-09 11:02             ` Sergey Senozhatsky [this message]
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=YqHTUdeZ8H0Lnf8E@google.com \
    --to=senozhatsky@chromium.org \
    --cc=axboe@kernel.dk \
    --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=minchan@kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=ngupta@vflare.org \
    --cc=regressions@lists.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.