From: Mike Galbraith <efault@gmx.de>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
lkml <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: Mel Gorman <mgorman@techsingularity.net>
Subject: Re: mm: LTP/memcg testcase regression induced by 8cd7c588decf..66ce520bb7c2 series
Date: Mon, 22 Nov 2021 08:41:08 +0100 [thread overview]
Message-ID: <813ba08684c710a4c3d82d7f894c37838a8cec5a.camel@gmx.de> (raw)
In-Reply-To: <723736b7736da3810cab582dee4591fec063618b.camel@gmx.de>
On Mon, 2021-11-22 at 07:46 +0100, Mike Galbraith wrote:
>
> #--------------------------------------------------------------------
> -------
> # Bug: The bug was, while forking mass processes, trigger
> memcgroup OOM,
> # then NULL pointer dereference may be hit.
> # Kernel: 2.6.25-rcX
> # Links: http://lkml.org/lkml/2008/4/14/38
> # Fix: commit e115f2d89253490fb2dbf304b627f8d908df26f1
> #--------------------------------------------------------------------
> -------
> test_1()
> {
> mkdir memcg/0/
> echo 0 > memcg/0/memory.limit_in_bytes
>
> ./memcg_test_1
>
> rmdir memcg/0/
>
> check_kernel_bug
> if [ $? -eq 1 ]; then
> tst_resm TPASS "no kernel bug was found"
> fi
> }
>
>
> I'm gonna just comment the little bugger out as obsolete and walk
> away.
test2() and test3() then pass, but test_4() hangs, and looks like it
should not, so...
-Mike
next prev parent reply other threads:[~2021-11-22 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99e779783d6c7fce96448a3402061b9dc1b3b602.camel@gmx.de>
2021-11-21 13:51 ` mm: LTP/memcg testcase regression induced by 8cd7c588decf..66ce520bb7c2 series Thorsten Leemhuis
2021-11-22 6:46 ` Mike Galbraith
2021-11-22 7:41 ` Mike Galbraith [this message]
2021-11-28 8:07 ` mm: LTP/memcg testcase regression induced by 8cd7c588decf..66ce520bb7c2 series #justforregzbot Thorsten Leemhuis
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=813ba08684c710a4c3d82d7f894c37838a8cec5a.camel@gmx.de \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=regressions@leemhuis.info \
--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 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).