linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
	 Linux-Next Mailing List <linux-next@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	 lkft-triage@lists.linaro.org, LTP List <ltp@lists.linux.it>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Peter Xu <peterx@redhat.com>,
	 Stephen Rothwell <sfr@canb.auug.org.au>,
	Arnd Bergmann <arnd@arndb.de>, Shakeel Butt <shakeelb@google.com>,
	 Roman Gushchin <roman.gushchin@linux.dev>,
	Ganesan Rajagopal <rganesan@arista.com>,
	 Baolin Wang <baolin.wang@linux.alibaba.com>,
	Michal Hocko <mhocko@suse.com>
Subject: [next] mm: overcommit_memory: failed - TFAIL: alloc passed, expected to fail
Date: Wed, 11 May 2022 22:33:00 +0530	[thread overview]
Message-ID: <CA+G9fYtKJ_a2rLSvxsYFrkUjNHpGeTn_xsL8kyz=-pBoeA+eXA@mail.gmail.com> (raw)

Following LTP test regressions were noticed on Linux next-20220511 tag on
all the devices.

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

Regressions found on x86 and arm64.

   ltp-mm-tests/overcommit_memory04
   ltp-mm-tests/overcommit_memory06
   ltp-mm-tests/overcommit_memory03
   ltp-mm-tests/min_free_kbytes
   ltp-mm-tests/overcommit_memory01
   ltp-mm-tests/oom01
   ltp-mm-tests/overcommit_memory05


mem.c:154: TFAIL: victim signalled: (9) SIGKILL
overcommit_memory.c:203: TFAIL: alloc passed, expected to fail
overcommit_memory.c:176: TINFO: malloc 7102100 kB successfully
overcommit_memory.c:203: TFAIL: alloc passed, expected to fail
overcommit_memory.c:176: TINFO: malloc 3523530 kB successfully

overcommit_memory.c:203: TFAIL: alloc passed, expected to fail
overcommit_memory.c:176: TINFO: malloc 8456472 kB successfully
overcommit_memory.c:203: TFAIL: alloc passed, expected to fail
overcommit_memory.c:176: TINFO: malloc 4283276 kB successfully
overcommit_memory.c:203: TFAIL: alloc passed, expected to fail
overcommit_memory.c:176: TINFO: malloc 2114118 kB successfully


metadata:
  git_ref: master
  git_repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
  git_sha: 6107040c99d5dfc920721c198d45ed2d639b113a
  git_describe: next-20220511
  kernel_version: 5.18.0-rc6
  kernel-config: https://builds.tuxbuild.com/291BWBU964yoppGqYfnVF8AJMg4/config
  build-url: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/pipelines/536448964
  artifact-location: https://builds.tuxbuild.com/291BWBU964yoppGqYfnVF8AJMg4
  toolchain: gcc-11


Full test log on x86:
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20220511/testrun/9438084/suite/ltp-mm-tests/test/overcommit_memory01/log
https://lkft.validation.linaro.org/scheduler/job/5012581#L10525


--
Linaro LKFT
https://lkft.linaro.org


                 reply	other threads:[~2022-05-11 17:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CA+G9fYtKJ_a2rLSvxsYFrkUjNHpGeTn_xsL8kyz=-pBoeA+eXA@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=ltp@lists.linux.it \
    --cc=mhocko@suse.com \
    --cc=peterx@redhat.com \
    --cc=rganesan@arista.com \
    --cc=roman.gushchin@linux.dev \
    --cc=sfr@canb.auug.org.au \
    --cc=shakeelb@google.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