All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Potapenko <glider@google.com>
To: Emanuel Czirai <correabuscar+kernAlbugs@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	bugzilla-daemon@kernel.org,  linux-mm@kvack.org,
	Eric Dumazet <edumazet@google.com>
Subject: Re: [Bug 217191] New: test_meminit: failures: 70 out of 130 / reference already released.
Date: Thu, 16 Mar 2023 10:29:09 +0100	[thread overview]
Message-ID: <CAG_fn=X3V=LKnGhAaeGkkzo9A_OpWckWKCqBWKhr5p3Jxv4T1A@mail.gmail.com> (raw)
In-Reply-To: <CAFjaU5sFgMLtLYW-5DoQOsAmntHq9BG2MX4JSeP7XZpZmXgEEw@mail.gmail.com>

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

>
>
>
>
>> May I ask what is the purpose of the config in question?
>>
> it's what I use on my home desktop PC(but merged the laptop .config into
> it, didn't have the time to test it on laptop so far yet) and I've enabled
> all tests to catch things early in the hopes of avoiding some potential
> btrfs filesystem corruption(for a third time, so far) if nothing else...
> but otherwise it'd be just reassuring to know that things are performing
> within their expected parameters (with tests passing and all). I don't
> remember why I've tried to keep modules at a minimum though.
>

I see, thanks for the explanation.
I think many tests in lib/ may produce strange warnings that are meant to
be parsed by human devs that know what to expect.
It would be nice to have them converted to KUNIT, but that's a long way to
go.

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

      reply	other threads:[~2023-03-16  9:29 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
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 [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='CAG_fn=X3V=LKnGhAaeGkkzo9A_OpWckWKCqBWKhr5p3Jxv4T1A@mail.gmail.com' \
    --to=glider@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@kernel.org \
    --cc=correabuscar+kernAlbugs@gmail.com \
    --cc=edumazet@google.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.