public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Michal Hocko via ltp <ltp@lists.linux.it>
To: Harshvardhan Jha <harshvardhan.j.jha@oracle.com>
Cc: ltp@lists.linux.it, cgroups@vger.kernel.org
Subject: Re: [LTP] Issue faced in memcg_stat_rss while running mainline kernels between 6.7 and 6.8
Date: Thu, 16 Jan 2025 10:06:04 +0100	[thread overview]
Message-ID: <Z4jL_GzJ98S_VYa3@tiehlicka> (raw)
In-Reply-To: <6ee7b877-19cc-4eda-9ea7-abf3af0a1b57@oracle.com>

On Thu 16-01-25 13:37:14, Harshvardhan Jha wrote:
> Hello Michal
> On 16/01/25 1:23 PM, Michal Hocko wrote:
> > Hi,
> >
> > On Wed 15-01-25 23:59:20, Petr Vorel wrote:
> >> Hi Harshvardhan,
> >>
> >> [ Cc cgroups@vger.kernel.org: FYI problem in recent kernel using cgroup v1 ]
> > It is hard to decypher the output and nail down actual failure. Could
> > somebody do a TL;DR summary of the failure, since when it happens, is it
> > really v1 specific?
> 
> The test ltp_memcg_stat_rss is indeed cgroup v1 specific.

What does this test case aims to test?

-- 
Michal Hocko
SUSE Labs

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-01-16  9:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19  8:25 [LTP] Issue faced in memcg_stat_rss while running mainline kernels between 6.7 and 6.8 Harshvardhan Jha via ltp
2024-12-05  6:48 ` Harshvardhan Jha via ltp
2025-01-15 12:52   ` Petr Vorel
2025-01-15 22:59     ` Petr Vorel
2025-01-16  7:53       ` Michal Hocko via ltp
2025-01-16  8:07         ` Harshvardhan Jha via ltp
2025-01-16  9:06           ` Michal Hocko via ltp [this message]
2025-01-16 10:04             ` Harshvardhan Jha via ltp
2025-01-16 10:35               ` Michal Hocko via ltp
2025-01-16 10:12             ` Petr Vorel
  -- strict thread matches above, loose matches on Subject: below --
2024-11-25 16:56 Harshvardhan Jha via ltp

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=Z4jL_GzJ98S_VYa3@tiehlicka \
    --to=ltp@lists.linux.it \
    --cc=cgroups@vger.kernel.org \
    --cc=harshvardhan.j.jha@oracle.com \
    --cc=mhocko@suse.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