mirror of
https://github.com/torvalds/linux
synced 2024-07-23 03:29:48 +00:00
925c86a19b
Add a new config option that controls building the buffer_head code, and select it from all file systems and stacking drivers that need it. For the block device nodes and alternative iomap based buffered I/O path is provided when buffer_head support is not enabled, and iomap needs a a small tweak to define the IOMAP_F_BUFFER_HEAD flag to 0 to not call into the buffer_head code when it doesn't exist. Otherwise this is just Kconfig and ifdef changes. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Link: https://lore.kernel.org/r/20230801172201.1923299-7-hch@lst.de Signed-off-by: Jens Axboe <axboe@kernel.dk>
28 lines
1.2 KiB
Plaintext
28 lines
1.2 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
config NILFS2_FS
|
|
tristate "NILFS2 file system support"
|
|
select BUFFER_HEAD
|
|
select CRC32
|
|
select LEGACY_DIRECT_IO
|
|
help
|
|
NILFS2 is a log-structured file system (LFS) supporting continuous
|
|
snapshotting. In addition to versioning capability of the entire
|
|
file system, users can even restore files mistakenly overwritten or
|
|
destroyed just a few seconds ago. Since this file system can keep
|
|
consistency like conventional LFS, it achieves quick recovery after
|
|
system crashes.
|
|
|
|
NILFS2 creates a number of checkpoints every few seconds or per
|
|
synchronous write basis (unless there is no change). Users can
|
|
select significant versions among continuously created checkpoints,
|
|
and can change them into snapshots which will be preserved for long
|
|
periods until they are changed back to checkpoints. Each
|
|
snapshot is mountable as a read-only file system concurrently with
|
|
its writable mount, and this feature is convenient for online backup.
|
|
|
|
Some features including atime, extended attributes, and POSIX ACLs,
|
|
are not supported yet.
|
|
|
|
To compile this file system support as a module, choose M here: the
|
|
module will be called nilfs2. If unsure, say N.
|