From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Theodore Ts'o <tytso@mit.edu>,
Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
caiqingfu <baicaiaichibaicai@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4@vger.kernel.org, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [bugzilla:219548] the kernel crashes when storing an EXT4 file system in a ZRAM device
Date: Thu, 12 Dec 2024 13:35:02 +0900 [thread overview]
Message-ID: <20241212043502.GI2091455@google.com> (raw)
In-Reply-To: <Z1pjJWkheibiaWuV@casper.infradead.org>
On (24/12/12 04:14), Matthew Wilcox wrote:
> > We've got two reports [1] [2] (could be the same person) which
> > suggest that ext4 may change page content while the page is under
> > write(). The particular problem here the case when ext4 is on
> > the zram device. zram compresses every page written to it, so if
> > the page content can be modified concurrently with zram's compression
> > then we can't really use zram with ext4.
>
> Do you set BLK_FEAT_STABLE_WRITES on zram?
Yes, zram sets BLK_FEAT_STABLE_WRITES and BLK_FEAT_SYNCHRONOUS.
next prev parent reply other threads:[~2024-12-12 4:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 3:58 [bugzilla:219548] the kernel crashes when storing an EXT4 file system in a ZRAM device Sergey Senozhatsky
2024-12-12 4:14 ` Matthew Wilcox
2024-12-12 4:35 ` Sergey Senozhatsky [this message]
2024-12-12 4:49 ` Christoph Hellwig
2024-12-12 5:37 ` Theodore Ts'o
2024-12-12 6:30 ` Sergey Senozhatsky
2024-12-12 7:35 ` Christoph Hellwig
2024-12-12 14:04 ` Theodore Ts'o
2024-12-12 14:12 ` Theodore Ts'o
2024-12-12 8:37 ` 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=20241212043502.GI2091455@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=baicaiaichibaicai@gmail.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
/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