From: Petr Vorel <pvorel@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PUSHED] zram01.sh: Workaround division by 0 on vfat on ppc64le
Date: Tue, 19 Sep 2023 11:25:44 +0200 [thread overview]
Message-ID: <20230919092544.GA166424@pevik> (raw)
In-Reply-To: <20230919091723.9278-1-rpalethorpe@suse.com>
Hi Richie,
> Repeatedly read /sys/block/zram*/mm_stat for 1 sec. This should fix bug
> on ppc64le on stable kernels, where mem_used_total is often 0.
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> Reviewed-by: Li Wang <liwang@redhat.com>
> Reviewed-by: Richard Palethorpe <rpalethorpe@suse.com>
> [rpalethorpe: s/loop/check/ suggested by Li]
> ---
> rpalethorpe:
> This may not fix the problem, but it can rule out a simple race
> condition.
thanks a lot for finishing the effort!
I was waiting for Cyril to have his ack.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2023-09-19 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 9:17 [LTP] [PUSHED] zram01.sh: Workaround division by 0 on vfat on ppc64le Richard Palethorpe via ltp
2023-09-19 9:25 ` Petr Vorel [this message]
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=20230919092544.GA166424@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@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