From: Lukas Czerner <lczerner@redhat.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
minchan@kernel.org, ngupta@vflare.org, Jan Kara <jack@suse.com>,
Ted Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: ext2/zram issue [was: Linux 5.19]
Date: Tue, 9 Aug 2022 11:53:48 +0200 [thread overview]
Message-ID: <20220809095348.lojwndf7uwolpfvo@fedora> (raw)
In-Reply-To: <YvIluTU6oFDpwQwK@google.com>
On Tue, Aug 09, 2022 at 06:15:37PM +0900, Sergey Senozhatsky wrote:
> On (22/08/09 11:12), Lukas Czerner wrote:
> > Hi Jiri,
> >
> > I've tried a quick xfstests run on ext2 on zram and I can't see any
> > issues like this so far. I will run a full test and report back in case
> > there is anything obvious.
>
> AFAICT this should be visible only when we are under memory pressure,
> so that direct reclaim from zs_malloc handle allocation call makes a
> difference.
>
True, I haven't seen the other email from Jiri, sorry about that. I can
confirm that under memory pressure it is in fact reproducible with
xfstests and also I can confirm that reverting
e7be8d1dd983156bbdd22c0319b71119a8fbb697 makes it go away.
But Jiri has a better repro already anyway.
Thanks!
-Lukas
next prev parent reply other threads:[~2022-08-09 9:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 21:43 Linux 5.19 Linus Torvalds
2022-08-01 12:47 ` Build regressions/improvements in v5.19 Geert Uytterhoeven
2022-08-02 9:14 ` Geert Uytterhoeven
2022-08-01 16:52 ` Linux 5.19 Tony Luck
2022-08-01 16:59 ` Linus Torvalds
2022-08-05 17:00 ` Please consider Linux 5.20 because it means "I love Linux" in Chinese (Re: Linux 5.19) Zhang Boyang
2022-08-07 17:21 ` David Laight
2022-08-09 6:03 ` ext2/zram issue [was: Linux 5.19] Jiri Slaby
2022-08-09 7:59 ` Jiri Slaby
2022-08-09 8:12 ` Jiri Slaby
2022-08-09 8:43 ` Sergey Senozhatsky
2022-08-09 9:11 ` Sergey Senozhatsky
2022-08-09 9:20 ` Sergey Senozhatsky
2022-08-09 10:20 ` Dmitry Rokosov
2022-08-09 11:53 ` Sergey Senozhatsky
2022-08-09 13:15 ` Aleksey Romanov
2022-08-09 13:29 ` Sergey Senozhatsky
2022-08-10 7:06 ` [PATCH] Revert "zram: remove double compression logic" Jiri Slaby
2022-08-10 7:14 ` Sergey Senozhatsky
2022-08-09 12:35 ` ext2/zram issue [was: Linux 5.19] Jiri Slaby
2022-08-09 12:45 ` Jiri Slaby
2022-08-09 12:57 ` Sergey Senozhatsky
2022-08-09 13:07 ` Sergey Senozhatsky
2022-08-09 9:12 ` Lukas Czerner
2022-08-09 9:15 ` Sergey Senozhatsky
2022-08-09 9:53 ` Lukas Czerner [this message]
[not found] ` <20220830214626.26544-1-charlie39@cock.li>
2022-08-31 7:55 ` Jiri Slaby
2022-08-11 14:02 ` [RESEND] Please consider name next Linux release "I love Linux" (Re: Linux 5.19) Zhang Boyang
2022-08-12 2:39 ` Baoquan He
2022-08-12 3:28 ` Huacai Chen
2022-08-12 6:31 ` Gao Xiang
2022-08-12 8:22 ` YanTeng Si
2022-08-13 17:17 ` Zhang Boyang
2022-08-14 15:22 ` WANG Xuerui
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=20220809095348.lojwndf7uwolpfvo@fedora \
--to=lczerner@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.com \
--cc=jirislaby@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=senozhatsky@chromium.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).