From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: Martin Doucha <mdoucha@suse.cz>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Minchan Kim <minchan@kernel.org>,
ltp@lists.linux.it, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Nitin Gupta <ngupta@vflare.org>, Jens Axboe <axboe@kernel.dk>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Yang Xu <xuyang2018.jy@fujitsu.com>
Subject: Re: [PATCH 0/1] Possible bug in zram on ppc64le on vfat
Date: Tue, 29 Nov 2022 13:38:30 +0900 [thread overview]
Message-ID: <Y4WMxqyVlAt0Sp3g@google.com> (raw)
In-Reply-To: <Y3zlrBQ8fgJyNm7G@pevik>
On (22/11/22 16:07), Petr Vorel wrote:
> > On 11. 11. 22 1:48, Sergey Senozhatsky wrote:
> > > On (22/11/10 15:29), Martin Doucha wrote:
[..]
> > > Can you try using /dev/urandom for dd, not /dev/zero?
> > > Do you still see zeroes in sysfs output or some random values?
>
> > After 50 test runs on a kernel where the issue is confirmed, I could not
> > reproduce the failure while filling the device from /dev/urandom instead of
> > /dev/zero. The test reported compression ratio around 1.8-2.5 which means
> > the memory usage reported by mm_stat was 10-13MB.
>
> Martin, thanks a lot for reruning tests. I wonder problems on /dev/zero is a
> kernel bug or just problem which should be workarounded.
Hmm. Does CONFIG_KASAN show anything interesting?
WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: Jens Axboe <axboe@kernel.dk>, Minchan Kim <minchan@kernel.org>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Nitin Gupta <ngupta@vflare.org>,
linux-kselftest@vger.kernel.org, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 0/1] Possible bug in zram on ppc64le on vfat
Date: Tue, 29 Nov 2022 13:38:30 +0900 [thread overview]
Message-ID: <Y4WMxqyVlAt0Sp3g@google.com> (raw)
In-Reply-To: <Y3zlrBQ8fgJyNm7G@pevik>
On (22/11/22 16:07), Petr Vorel wrote:
> > On 11. 11. 22 1:48, Sergey Senozhatsky wrote:
> > > On (22/11/10 15:29), Martin Doucha wrote:
[..]
> > > Can you try using /dev/urandom for dd, not /dev/zero?
> > > Do you still see zeroes in sysfs output or some random values?
>
> > After 50 test runs on a kernel where the issue is confirmed, I could not
> > reproduce the failure while filling the device from /dev/urandom instead of
> > /dev/zero. The test reported compression ratio around 1.8-2.5 which means
> > the memory usage reported by mm_stat was 10-13MB.
>
> Martin, thanks a lot for reruning tests. I wonder problems on /dev/zero is a
> kernel bug or just problem which should be workarounded.
Hmm. Does CONFIG_KASAN show anything interesting?
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-11-29 4:38 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 19:11 [PATCH 0/1] Possible bug in zram on ppc64le on vfat Petr Vorel
2022-11-07 19:11 ` [LTP] " Petr Vorel
2022-11-07 19:11 ` [PATCH 1/1] zram01.sh: Workaround division by 0 on vfat on ppc64le Petr Vorel
2022-11-07 19:11 ` [LTP] " Petr Vorel
2022-11-21 7:14 ` Li Wang
2022-11-21 8:59 ` Petr Vorel
2022-11-21 8:59 ` Petr Vorel
2023-09-18 9:38 ` Richard Palethorpe
2022-11-07 21:25 ` [PATCH 0/1] Possible bug in zram on ppc64le on vfat Minchan Kim
2022-11-07 21:25 ` [LTP] " Minchan Kim
2022-11-07 21:47 ` Petr Vorel
2022-11-07 21:47 ` [LTP] " Petr Vorel
2022-11-07 22:42 ` Petr Vorel
2022-11-07 22:42 ` [LTP] " Petr Vorel
2022-11-08 1:05 ` Sergey Senozhatsky
2022-11-08 1:05 ` [LTP] " Sergey Senozhatsky
2022-11-09 22:08 ` Petr Vorel
2022-11-09 22:08 ` [LTP] " Petr Vorel
2022-11-10 23:04 ` Minchan Kim
2022-11-10 23:04 ` [LTP] " Minchan Kim
2022-11-11 9:29 ` Petr Vorel
2022-11-11 9:29 ` [LTP] " Petr Vorel
2022-11-10 14:29 ` Martin Doucha
2022-11-10 14:29 ` [LTP] " Martin Doucha
2022-11-11 0:48 ` Sergey Senozhatsky
2022-11-11 0:48 ` [LTP] " Sergey Senozhatsky
2022-11-21 9:41 ` Petr Vorel
2022-11-21 9:41 ` [LTP] " Petr Vorel
2022-11-22 14:56 ` Martin Doucha
2022-11-22 14:56 ` [LTP] " Martin Doucha
2022-11-22 15:07 ` Petr Vorel
2022-11-22 15:07 ` [LTP] " Petr Vorel
2022-11-29 4:38 ` Sergey Senozhatsky [this message]
2022-11-29 4:38 ` Sergey Senozhatsky
2023-05-02 15:23 ` Martin Doucha
2023-05-02 15:23 ` [LTP] " Martin Doucha
2022-11-11 9:18 ` Petr Vorel
2022-11-11 9:18 ` [LTP] " Petr Vorel
2023-08-04 6:37 ` Ian Wienand
2023-08-04 6:37 ` [LTP] " Ian Wienand
2023-08-07 4:44 ` Ian Wienand
2023-08-07 4:44 ` [LTP] " Ian Wienand
2023-08-07 5:19 ` Sergey Senozhatsky
2023-08-07 5:19 ` [LTP] " Sergey Senozhatsky
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=Y4WMxqyVlAt0Sp3g@google.com \
--to=senozhatsky@chromium.org \
--cc=axboe@kernel.dk \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=pvorel@suse.cz \
--cc=xuyang2018.jy@fujitsu.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 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.