diff options
| author | Qu Wenruo <[email protected]> | 2024-05-21 19:27:31 +0930 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2024-05-21 15:27:17 +0200 |
| commit | 440861b1a03c72cc7be4a307e178dcaa6894479b (patch) | |
| tree | 757f8922e8f73389c40381236efca047bd5cd909 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | dddff821b660e08eb8418cfd3909e61204804534 (diff) | |
btrfs: re-introduce 'norecovery' mount option
Although 'norecovery' mount option was marked as deprecated for a long
time and a warning message was printed during the deprecation window,
it's still actively utilized by several projects that need a safer way
to mount a btrfs without any writes.
Furthermore this 'norecovery' mount option is supported by other major
filesystems, which makes it less clear what's our motivation to remove
it.
Re-introduce the 'norecovery' mount option, and output a message to recommend
'rescue=nologreplay' option.
Link: https://lore.kernel.org/linux-btrfs/ZkxZT0J-z0GYvfy8@gardel-login/#t
Link: https://github.com/systemd/systemd/pull/32892
Link: https://bugzilla.suse.com/show_bug.cgi?id=1222429
Reported-by: Lennart Poettering <[email protected]>
Reported-by: Jiri Slaby <[email protected]>
Fixes: a1912f712188 ("btrfs: remove code for inode_cache and recovery mount options")
CC: [email protected] # 6.8+
Reviewed-by: Johannes Thumshirn <[email protected]>
Signed-off-by: Qu Wenruo <[email protected]>
Reviewed-by: David Sterba <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions