linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Marc Dionne <marc.c.dionne@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: Boot hang with 5.4-rc1, bisected to c5665868183f
Date: Thu, 3 Oct 2019 10:13:28 +0100	[thread overview]
Message-ID: <20191003091327.GC21629@arrakis.emea.arm.com> (raw)
In-Reply-To: <CAB9dFdtVzo2C_8h+Qe144mrhBRZp5TkdiudwXsfZo5fCAWWj_g@mail.gmail.com>

On Wed, Oct 02, 2019 at 07:26:51PM -0300, Marc Dionne wrote:
> 5.4-rc1 hangs early on boot for me; the stack trace that I could
> manage to see on screen suggested something kmemleak related, and it
> was fairly quick to bisect it down to commit c5665868183f ("mm:
> kmemleak: use the memory pool for early allocations").
> 
> Several call stacks periodically go by on screen, an interesting one
> is (manually transcribed):
> 
> RIP: 0010:_raw_write_unlock_irqrestore+0x15/0x20
>   find_and_remove_object+0x84/0x90
>   delete_object_full+0x10/0x20
>   __kmemleak_do_cleanup+0x2d/0x50
>   kmemleak_do_cleanup+0x59/0x60
>   process_one_work+0x1a4/0x3c0
>   worker_thread+0x50/0x3c0
> ...
> 
> Config is attached.

Thanks for the report. This was also mentioned here:

http://lkml.kernel.org/r/2ac37341-097e-17a2-fb6b-7912da9fa38e@ozlabs.ru

I'll have a look. It seems to only happen on the kmemleak disabling
path (I managed to reproduce it as well).

-- 
Catalin

      reply	other threads:[~2019-10-03  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 22:26 Boot hang with 5.4-rc1, bisected to c5665868183f Marc Dionne
2019-10-03  9:13 ` Catalin Marinas [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=20191003091327.GC21629@arrakis.emea.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marc.c.dionne@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;
as well as URLs for NNTP newsgroup(s).