Re: [PATCH v3 00/12] ftrfs: Fault-Tolerant Radiation-Robust Filesystem
From: Pedro Falcato
Date: Tue Apr 14 2026 - 06:28:12 EST
On Tue, Apr 14, 2026 at 02:07:13PM +0200, Aurelien DESBRIERES wrote:
> This is v3 of the FTRFS patch series. FTRFS is a Linux kernel filesystem
> designed for dependable storage in radiation-intensive environments,
> implementing Reed-Solomon FEC at the filesystem block level for in-place
> correction of silent bit flips on single-device embedded systems (MRAM,
> NOR flash) without external redundancy.
>
> Based on: Fuchs, Langer, Trinitis - ARCS 2015, TU Munich / MOVE-II CubeSat.
> Full text: https://www.cfuchs.net/chris/publication-list/ARCS2015/FTRFS.pdf
>
> Changes since v2 (<20260413230601.525400-1-aurelien@xxxxxxxxxxxx>):
>
> - iomap IO path: replace buffer_head based read/write with iomap API
> as requested by Matthew Wilcox. Implements ftrfs_iomap_begin/end,
> iomap_writeback_ops (writeback_range/writeback_submit), and uses
> iomap_bio_read_ops for the read path. buffer_head is retained for
> metadata IO (inode table, directory blocks) as discussed.
>
> - rename: implement ftrfs_rename in namei.c. Handles same-dir and
> cross-dir rename for files and directories, updates '..' entries
> and nlink counts. RENAME_EXCHANGE and RENAME_WHITEOUT return
> -EINVAL (not supported in v3).
>
> - RS FEC decoder: implement full RS(255,239) decoder in edac.c using
> Berlekamp-Massey error locator polynomial, Chien search, and Forney
> algorithm for in-place correction. Corrects up to 8 symbol errors
> per 255-byte subblock. Returns -EBADMSG if uncorrectable.
>
> - Radiation Event Journal: persistent ring buffer of 64 x 24 bytes
> in the superblock reserved area. Records block number, timestamp
> (ns), symbols corrected, and per-entry CRC32 for each RS correction
> event. Written under spinlock via ftrfs_log_rs_event(). No existing
> Linux filesystem provides this filesystem-level radiation event
> history - VxWorks HRFS, btrfs scrub, and NVMe SMART all operate
> at different layers.
>
> AI tooling disclosure (Documentation/process/coding-assistants.rst):
> Assisted-by: Claude:claude-sonnet-4-6
> The submitter takes full responsibility for all code, has reviewed,
> tested, and debugged every patch.
I was going to ask if you were on the world's strongest stimulant but, yeah,
this also makes sense.
3 versions in a day and no reply to review comments, no usecase, just vibes,
AI ones at that. This latest batch even got the LLM to hallucinate my old
email address.
Naturally,
Nacked-by: Pedro Falcato <pfalcato@xxxxxxx>
Please pick this up to every patch if you get to send more slop versions.
--
Pedro