From: linuxtestproject.agent@gmail.com
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] syscalls/madvise06: Fix sporadic not enough RAM TCONFs
Date: Wed, 27 May 2026 13:06:52 +0000 [thread overview]
Message-ID: <20260527130652.4138-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260527103756.448843-1-chrubis@suse.cz>
Hi Cyril,
On Wed, 27 May 2026 12:37:56 +0200, Cyril Hrubis wrote:
> syscalls/madvise06: Fix sporadic not enough RAM TCONFs
> On systems with <= 2GB RAM the test produced sporadic TCONFs. That is
> because even if the test setup does sync() and drops caches the system
> starts fauting in pages immediatelly after caches were dropped. It may
> easily happen that system may fault in a few hundred of MBs of memory
> betwen the write to drop_caches and the time sysinfo() syscall returns.
Three typos in the commit body: "fauting" -> "faulting", "immediatelly"
-> "immediately", "betwen" -> "between".
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
Duplicate Reviewed-by tag.
[...]
---
Note:
The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.
Regards,
LTP AI Reviewer
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-05-27 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 10:37 [LTP] [PATCH] syscalls/madvise06: Fix sporadic not enough RAM TCONFs Cyril Hrubis
2026-05-27 11:22 ` Li Wang
2026-05-27 11:29 ` Petr Vorel
2026-05-27 12:13 ` Cyril Hrubis
2026-05-27 12:17 ` Petr Vorel
2026-05-27 13:06 ` linuxtestproject.agent [this message]
2026-05-27 13:24 ` [LTP] " 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=20260527130652.4138-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=chrubis@suse.cz \
--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.