All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: ltp@lists.linux.it
Subject: [LTP] Holidays and LTP release
Date: Wed, 20 Jan 2021 15:01:30 +0530	[thread overview]
Message-ID: <CA+G9fYvRqOH7D04NHwPQNXKyMzak5bDo=GN3k13tcwV3bwN5Yw@mail.gmail.com> (raw)
In-Reply-To: <db866679-a5e8-35d6-f57a-18a202c7937b@suse.cz>

On Thu, 14 Jan 2021 at 19:44, Martin Doucha <mdoucha@suse.cz> wrote:
>
> On 14. 01. 21 12:12, Naresh Kamboju wrote:
> > on x86_64:
> > The ioctl_sg01 test killed and reported failed.
> >
> > tst_test.c:1263: TINFO: Timeout per run is 0h 15m 00s
> > ioctl_sg01.c:81: TINFO: Found SCSI device /dev/sg1
> > [  332.383394] ioctl_sg01 invoked oom-killer:
>
> Looks like the safety margin in tst_pollute_memory() is too small. Edit
> lib/tst_memutils.c and try setting the "safety" variable on line 23 to a
> higher value. I'd recommend something like MAX(4096 pages, 64MB).

do you mean something like this ?
But this change did not solve the problem (ioctl_sg01) i have reported.

diff --git a/lib/tst_memutils.c b/lib/tst_memutils.c
index f134d90c9..00bf45e9c 100644
--- a/lib/tst_memutils.c
+++ b/lib/tst_memutils.c
@@ -20,7 +20,7 @@ void tst_pollute_memory(size_t maxsize, int fillchar)
        struct sysinfo info;

        SAFE_SYSINFO(&info);
-       safety = 4096 * SAFE_SYSCONF(_SC_PAGESIZE) / info.mem_unit;
+       safety = 8192 * SAFE_SYSCONF(_SC_PAGESIZE) / info.mem_unit;

        if (info.freeswap > safety)
                safety = 0;


After the above change the test case ioctl_sg01 fails intermittently
when running
multiple times.
https://lkft.validation.linaro.org/scheduler/job/2170593#L1357


- Naresh

  reply	other threads:[~2021-01-20  9:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 12:18 [LTP] Holidays and LTP release Cyril Hrubis
2021-01-06 12:19 ` Cyril Hrubis
2021-01-07 11:51   ` Cyril Hrubis
2021-01-08  1:23     ` Yang Xu
2021-01-08 13:28       ` Cyril Hrubis
2021-01-11 14:38     ` Cyril Hrubis
2021-01-12 10:29       ` Petr Vorel
2021-01-13  8:57   ` =?unknown-8bit?q?K=C3=B6ry?= Maincent
2021-01-14 11:12     ` Naresh Kamboju
2021-01-14 14:14       ` Martin Doucha
2021-01-20  9:31         ` Naresh Kamboju [this message]
2021-01-20 10:26           ` Cyril Hrubis
2021-01-20 13:33             ` Cyril Hrubis
2021-01-14 14:36       ` Cyril Hrubis
2021-01-15  8:27         ` Naresh Kamboju
2021-01-15 14:00           ` Cyril Hrubis
2021-01-15 14:27             ` Cyril Hrubis
2021-01-14  9:17   ` Martin Doucha
2021-01-14 10:41     ` Cyril Hrubis
2021-01-14 15:01 gengcixi
2021-01-15 15:08 gengcixi
2021-01-19 10:43 ` Cyril Hrubis

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+G9fYvRqOH7D04NHwPQNXKyMzak5bDo=GN3k13tcwV3bwN5Yw@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=ltp@lists.linux.it \
    /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.