All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Potapenko <glider@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: correabuscar+kernAlbugs@gmail.com, bugzilla-daemon@kernel.org,
	 linux-mm@kvack.org
Subject: Re: [Bug 217191] New: test_meminit: failures: 70 out of 130 / reference already released.
Date: Wed, 15 Mar 2023 14:57:59 +0100	[thread overview]
Message-ID: <CAG_fn=UH2QqshE6s4SvRKmuCwzTpcXc_9gieU00dfZ3m-HEAZg@mail.gmail.com> (raw)
In-Reply-To: <20230314144145.07a3e680362eb77061fe6d0e@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 472 bytes --]

Hi Emmanuel,

Can you please share the kernel config where the problem is reproducible,
along with the full dmesg?

I think "test_meminit: failures: 70 out of 130" is a red herring, the
kernel probably does not enable memory initialization, that's why the tests
are failing.
We could see that from the "mem auto-init" line in the dmesg, but it got
stripped away.
The leaked reference probably belongs to lib/test_ref_tracker.c, which is a
completely different test suite.

[-- Attachment #2: Type: text/html, Size: 598 bytes --]

  reply	other threads:[~2023-03-15 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-217191-27@https.bugzilla.kernel.org/>
2023-03-14 21:41 ` [Bug 217191] New: test_meminit: failures: 70 out of 130 / reference already released Andrew Morton
2023-03-15 13:57   ` Alexander Potapenko [this message]
2023-03-15 17:22     ` Emanuel Attila Czirai
2023-03-15 17:46       ` Alexander Potapenko
2023-03-15 22:33         ` Emanuel Czirai
2023-03-16  9:29           ` Alexander Potapenko

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='CAG_fn=UH2QqshE6s4SvRKmuCwzTpcXc_9gieU00dfZ3m-HEAZg@mail.gmail.com' \
    --to=glider@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@kernel.org \
    --cc=correabuscar+kernAlbugs@gmail.com \
    --cc=linux-mm@kvack.org \
    /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.