From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm1-f49.google.com (mail-wm1-f49.google.com [209.85.128.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 14B133E63AF for ; Tue, 14 Apr 2026 12:07:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.128.49 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776168463; cv=none; b=qIbBmycLQvmNCcSp4ODvYKN1cER7EhPyyJBlOTIu4cbxb9x3n1bJGlWBh6ri4BRMwKrdchP9LbSr9wM9MOlT4wRqj2YkDFM0ufNcNL7/0igTaK8keXiaEn5bTYNUHlp9NdZkoZM7uWk4Dnl9uaqbeOrK/EELJcLbqVfvbT79BTY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776168463; c=relaxed/simple; bh=U2wZqUTCK83/IxPTnPQYhXtAolBiCnHNAgHzDmSEW7M=; h=From:To:Cc:Subject:In-Reply-To:References:Content-Type:Date: Message-Id; b=j8RIUvrnDuWUyqG6r4FkrDwSlq0Z/10HXvxgqMwHbmzUl7vuyLw6VBVgvkJK5CI5fcrBUo09mNyg50z90ts4MGodfNLnZVLKG+xKSNGrU1IwdtEWRhdzp7N97rzUB3B6NJugvq/+aq92BmuEu/0b2n8qlxyAWmzNg+bAzy9jP/Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=hackers.camp; spf=pass smtp.mailfrom=gmail.com; arc=none smtp.client-ip=209.85.128.49 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=hackers.camp Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-wm1-f49.google.com with SMTP id 5b1f17b1804b1-488ac04e13dso6946545e9.1 for ; Tue, 14 Apr 2026 05:07:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776168460; x=1776773260; h=message-id:date:references:in-reply-to:subject:cc:to:from:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=rqwumVkV7OjtVVY6WSleaCUArhIFQ0xmlwKBOzFdjDs=; b=CUwjR+0v2DhPp+fgj39gZYNJXXyndtJ9ignUaNwK7kc2EIBv4Ysq8TovBKw872jnna WktDPW6l6VWLf299QL0z1ip8YQVJvjiXn/C7kdQBQjTFI0kkyAOCCr0fiYiKDTTq6//I MEl/00r9GzsIUYroQBOLS1neNowBLt7nu3q+L9HF7HP8Zr//LseSqMjIdlowjIuTOoCV LIK83SXZQYrIR2c9X6w/itM0BUiSS175/tcbEqy9XROVT9ENIAcCiOm91oJO1aRJ99y3 qEQXmzoAl7Hf2Tm5KJ5kCVpjq5ql1YEtI+6K+/k5gRmzUs5wot7cOkckvagnLmsAtquv F0Ww== X-Forwarded-Encrypted: i=1; AFNElJ8JNpsY7qk7jGQ5EZpjKtOp8UI/I7yC5Okfh5J/cjjVND3UCIjueQLdbQxCCtHPrbe8HILbts2rPj2qGr8=@vger.kernel.org X-Gm-Message-State: AOJu0Yy7Xi3qilhrBh4YtrHo7pnaVIy7IGj53ZD0JmiipWv9nim6fPAH slfPIYkcolWUevm9eLBFYZq+cOWHgAYrmm3PtuhdaxUHrfGr9u1rFBR9 X-Gm-Gg: AeBDiesLjAp1e5he63zFf3IysxkOPRWxKCswBujQlD8zwJ8CYeNro7RheA6YffIJmIK MuwE2sVKgbuVYIStIpdfAKwDcDcvd7l3BRylVXXyog/ji9U3UnDD9cz/HbXhzrr//zJIefVux3H aWxtwr0TXN5R9lY8J/QD3hFINaH0Jq/Y6ph4CV+jozif4viweW2dCvFsdtV94I5Yg+IK9phVEcZ ELQHFVVkLgpYY+4wsHQg1rP3kJB/sN1+5wew9swluwjffeWaY3oaC8SI/uM4tfVxsfX76e7L7C0 cFhB8ut2t0X4k1Rcagb62n/kjPGJbNlg0zkv/XcMKjw1A3SyZRMgiBh622O6UDUbrP0GQrfYt7j wr9lus5C6EaaonHCLEk1gS8ZLyZ4ul6uJV8WgVWr2dZlv4ivcuyWsSuV4sgLd7Grw5ZR/xRO02j LPYplme3CaavXhOyADY1ko+dVJsdjyB4chXHHrbrozQEZxvSHM52ZA6pGXbNR54hFi2YL4zvlhQ baYOiwdPi8v2icZ X-Received: by 2002:a05:600c:b85:b0:488:afb4:b98c with SMTP id 5b1f17b1804b1-488d68b3827mr129827555e9.3.1776168460348; Tue, 14 Apr 2026 05:07:40 -0700 (PDT) Received: from hackers.camp ([2a01:cb1c:784:2f00:708:2805:7128:7a75]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-488ede1513csm51560435e9.2.2026.04.14.05.07.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Apr 2026 05:07:39 -0700 (PDT) Received: (nullmailer pid 9702 invoked by uid 1000); Tue, 14 Apr 2026 13:46:48 -0000 From: Aurelien DESBRIERES To: Pedro Falcato Cc: Joshua Peisach , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, willy@infradead.org, djwong@kernel.org, adilger@dilger.ca, xiang@kernel.org Subject: Re: [PATCH v3 00/12] ftrfs: Fault-Tolerant Radiation-Robust Filesystem In-Reply-To: References: <20260413230601.525400-1-aurelien@hackers.camp> <20260414120726.5713-1-aurelien@hackers.camp> Content-Type: text/plain; charset=UTF-8 Date: Tue, 14 Apr 2026 15:46:48 +0200 Message-Id: <1776174408.705089.9701.nullmailer@me> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: On Tue, Apr 14, 2026 at 12:28:33PM +0100, Pedro Falcato wrote: > Yes, a paper is provided. However, when I asked for a usecase I > really did mean: "is anyone going to actually use this?". > > Good answers (IMHO): > - "Yes, we have a couple of planned users for this" > - "Yes, this has been maintained out-of-tree for X months/years" > - "Yes, we are using it" Fair. Let me give a more concrete answer. The implementation is currently maintained out-of-tree and validated in an arm64 HPC cluster running Slurm 25.11.4 on Yocto Styhead 5.1, kernel 7.0. This is an active, working deployment, not a paper prototype: https://github.com/roastercode/yocto-hardened/tree/arm64-ftrfs For planned users, the target environments where Linux is actively used and where radiation-induced SEU is a documented operational concern include: - Embedded Linux on nanosatellites and CubeSats. The MOVE-II mission at TU Munich is the direct origin of the FTRFS design. Commercial CubeSat operators increasingly use Linux-capable SoCs (i.MX, Zynq) precisely because of the ecosystem, and SEU rates on MRAM in LEO are well-documented. - Robotics in high-radiation environments. Industrial robots deployed in nuclear facilities (decommissioning, inspection) and planetary rovers operate in radiation environments where silent bit flips are a real operational risk. Linux is the dominant OS in these systems. - Space HPC. There is growing interest in deploying HPC workloads in orbit for Earth observation and AI inference at the edge. European space industry players (including Thales Alenia Space, a known Linux embedded user) are actively exploring this. A radiation-tolerant filesystem is a missing piece of that stack. None of these are signed contracts I can point to today. This is an RFC, not a production submission. The question for the community is whether the technical problem is real and the approach sound — both of which are independent of whether I have a purchase order in hand. The radio silence you mention was a process failure on my part. Replies to v1 review comments should have come before v2, not after v3. That is corrected now. Aurelien DESBRIERES