From: Ivan Babrou <ivan@cloudflare.com>
To: Yu Zhao <yuzhao@google.com>
Cc: Linux MM <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan@kernel.org>,
Nitin Gupta <ngupta@vflare.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: zram corruption due to uninitialized do_swap_page fault
Date: Fri, 11 Mar 2022 14:36:51 -0800 [thread overview]
Message-ID: <CABWYdi3iJ45pSgj-OrxATVXR7-MHb3DZ-UkERPvo9L=h_qtzgA@mail.gmail.com> (raw)
In-Reply-To: <CAOUHufb=GQaX_2Bp2YfY4ntBZj8iwb8z9mvxUFXw+KkySRu+KA@mail.gmail.com>
On Fri, Mar 11, 2022 at 2:30 PM Yu Zhao <yuzhao@google.com> wrote:
>
> On Fri, Mar 11, 2022 at 12:52 PM Ivan Babrou <ivan@cloudflare.com> wrote:
> >
> > Hello,
> >
> > We're looking into using zram, but unfortunately we ran into some
> > corruption issues.
>
> Kernel version(s) please?
You can see 5.16 in dmesg output. I've also replicated on 5.17-rc7 and
5.15.26. The latter is the LTS version we use in production, where
coredumps and rocksdb corruptions were observed.
next prev parent reply other threads:[~2022-03-11 22:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 19:51 Ivan Babrou
2022-03-11 22:30 ` Yu Zhao
2022-03-11 22:36 ` Ivan Babrou [this message]
2022-03-14 22:40 ` Minchan Kim
2022-03-15 0:24 ` Ivan Babrou
2022-03-15 4:34 ` Hillf Danton
2022-03-15 4:54 ` Ivan Babrou
2022-03-15 4:18 ` Ivan Babrou
2022-03-15 6:57 ` Minchan Kim
2022-03-15 8:30 ` David Hildenbrand
2022-03-15 22:09 ` Minchan Kim
2022-03-16 18:26 ` Ivan Babrou
2022-03-18 16:30 ` Ivan Babrou
2022-03-18 17:32 ` Minchan Kim
2022-03-18 18:54 ` Minchan Kim
2022-03-25 2:10 ` Ivan Babrou
2022-03-25 8:33 ` David Hildenbrand
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='CABWYdi3iJ45pSgj-OrxATVXR7-MHb3DZ-UkERPvo9L=h_qtzgA@mail.gmail.com' \
--to=ivan@cloudflare.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=senozhatsky@chromium.org \
--cc=yuzhao@google.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