Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp3520541pxb; Mon, 4 Apr 2022 19:43:13 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwP4wPqipYV2xuZpp/bq4UjYQm4PFyMzHPe1j/WxufTQC2a3NYvtCjkxf9l4bhsgTKXUUKI X-Received: by 2002:a17:902:bb85:b0:154:9a18:4a6d with SMTP id m5-20020a170902bb8500b001549a184a6dmr1302550pls.62.1649126592885; Mon, 04 Apr 2022 19:43:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649126592; cv=none; d=google.com; s=arc-20160816; b=qJj2yRTcl8PfnsAvPM4HcYBMRvD9Rt76ZHTAQA+qj1kUfxxduxRXC5mNg4YDELewkQ 0k/xUnoZRXHFsAbxIJysS9biKvz2NnSM1EHaCHbn/aax/AxUvbUSHHBzowt6E+QO5Aow rcZCW5PnMUFo9paPhuXpsGKjlzWKwdqLxbG56agiob2h7ibpVpmG8TGaXrQKrwXCDQ62 ZYXyd/YlDTSWnI9RRke9l51RkZKbXUmj6lckKGQ4LakyoyI0BHS9V3JmVH65pHEiPkRf Hviyt9JgqcgKMu1/f412A7DScLgmgPIKriA2e87CfOmdO5UhtwuHtJep3aAhEaH+K6tw 0lPg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=wC86gbUg8Q4G9+5Yh9zn7w8RySmSqCqeIm64QO9mOtE=; b=nuOOeumKAVk3tP8zojWopICsRM0U/4gN831d+Fbz6F6XzT3C+hVD28ehdFfsU1wgGY knuNa4vaCLFcBuQ7KK6PjFKbZBa9eHc6nTF2moC25FIPT8nOTK0hPOmPTd4RbYgWC1Ik EmVsjy1APuBOZyuo9jYivILOf7CG1qWWK0ecflehdY0QUAh+i4uOCU8Rvycr4+4Qhvz+ G8KWhIQvoMhKRw4BV3PdOumMuERac7W0ggs2a+pcEvzrTanX2M2l4DwaA73CKuCRtBPk 7r1RgDH7yvq0zA8uM3M5jF3Cfr8R/fMwlxWoPc9OL5a7UvmVWHCG1bBeloaOozRxsUDy AXBw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=RRl3Ow3d; dkim=neutral (no key) header.i=@suse.cz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id t22-20020a634616000000b003993a4f24desi3103453pga.441.2022.04.04.19.43.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 Apr 2022 19:43:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=RRl3Ow3d; dkim=neutral (no key) header.i=@suse.cz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id D058C14076B; Mon, 4 Apr 2022 18:06:38 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349235AbiDDNHN (ORCPT + 99 others); Mon, 4 Apr 2022 09:07:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41988 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348961AbiDDNHK (ORCPT ); Mon, 4 Apr 2022 09:07:10 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5ACD62C0; Mon, 4 Apr 2022 06:05:14 -0700 (PDT) Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out1.suse.de (Postfix) with ESMTP id 0A892210EE; Mon, 4 Apr 2022 13:05:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1649077513; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wC86gbUg8Q4G9+5Yh9zn7w8RySmSqCqeIm64QO9mOtE=; b=RRl3Ow3dGGV/s0GtOYqND8FDvBjDPcuucOKEmxJhaBcg62IE3bwOhSXMJciuwie00la3Dt vIfvgni/VDrCBhutbnKt8xpngOFzHx/wcKTCF8tYsbDVCtNQg+wwBylUkJIqgBiNZBAaT7 Sh95Qo2GYHO9iiR89s0vrUg4OpctFYA= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1649077513; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wC86gbUg8Q4G9+5Yh9zn7w8RySmSqCqeIm64QO9mOtE=; b=97OjsjXSzuzMn9M2iOy1/9cSLKyhZw16LE9piwwkUvv526LZ2e1h0R4Z7Gx6tzk2drEP5w WAJgVKn6SFSswSAQ== Received: from quack3.suse.cz (unknown [10.100.224.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id E2D46A3B82; Mon, 4 Apr 2022 13:05:12 +0000 (UTC) Received: by quack3.suse.cz (Postfix, from userid 1000) id DD60CA0615; Mon, 4 Apr 2022 15:05:11 +0200 (CEST) Date: Mon, 4 Apr 2022 15:05:11 +0200 From: Jan Kara To: Pavel Machek Cc: Willy Tarreau , Jan Kara , Matthew Wilcox , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, reiserfs-devel@vger.kernel.org Subject: Re: Is it time to remove reiserfs? Message-ID: <20220404130511.rq7evchtxk7s7dre@quack3.lan> References: <20220222100408.cyrdjsv5eun5pzij@quack3.lan> <20220402105454.GA16346@amd> <20220404085535.g2qr4s7itfunlrqb@quack3.lan> <20220404100732.GB1476@duo.ucw.cz> <20220404101802.GB8279@1wt.eu> <20220404105828.GA7162@duo.ucw.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220404105828.GA7162@duo.ucw.cz> X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello! On Mon 04-04-22 12:58:28, Pavel Machek wrote: > > So maybe you're right and there are still a bit more than expected out > > there. However I really think that most users who still have one are in > > the same situation as I am, they're not aware of it. So aside big fat > > warnings at mount time (possibly with an extra delay), there's nothing > > that will make that situation change. > > > > At the very least disabling it by default in Kconfig and in distros > > should be effective. I really don't think that there are still users > > who regularly update their system and who have it on their rootfs, but > > still having data on it, yes, possibly. The earlier they're warned, > > the better. > > I guess we should start by making sure that distributions don't use it > by default. Big fat warning + delay is a bit harsh for that, talking > to them should be enough at this point :-). > > Someone start with Arch Linux ARM. Yeah, I will write them and CC you. Thanks for notifying me. Honza -- Jan Kara SUSE Labs, CR