From: Christoph Hellwig <hch@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
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: Wed, 11 Dec 2024 23:35:40 -0800 [thread overview]
Message-ID: <Z1qSTM_Eibvw0bM5@infradead.org> (raw)
In-Reply-To: <20241212053739.GC1265540@mit.edu>
On Thu, Dec 12, 2024 at 12:37:39AM -0500, Theodore Ts'o wrote:
> More generally, any file system which uses the buffer cache, and
> doesn't use jbd2 to control when writeback happens, I think is going
> to be at risk with a block device which requires stable writes. The
> only way to fix this, really, is to have the buffer cache code copy
> the data to a bounce buffer, and then issue the write from the bounce
> buffer.
Should there be a pr_warn_once when using a file systems using the legacy
buffer cache interfaces on a device that requires stable pages?
next prev parent reply other threads:[~2024-12-12 7: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
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 [this message]
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=Z1qSTM_Eibvw0bM5@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=baicaiaichibaicai@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=senozhatsky@chromium.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 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.