Received: by 10.223.185.116 with SMTP id b49csp5637853wrg; Wed, 7 Mar 2018 15:33:19 -0800 (PST) X-Google-Smtp-Source: AG47ELupEMkd6v3CiH3frMWcZ+OSlg66RfkmKNB9gV5XRgamRQhrXPHWnbXc5zE0L0PevSGQoK7H X-Received: by 10.98.160.142 with SMTP id p14mr24506607pfl.134.1520465599620; Wed, 07 Mar 2018 15:33:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520465599; cv=none; d=google.com; s=arc-20160816; b=YQnhj9HcnT717FjRekvNgZEetdVH7fDVexruLEiIAWhK/ZA08ea7kn25W0GRum1OAM nh8hzP+llE9/edPoupvpaocUW/LG2AmeA9arJtFPWWpjEs0XYSymrTFjzUygppnrFqSX AJUgLZL+ZEGG3JuY1bce+/Evnkt2oz4/tF7AtIcFAckiQUSPuD1p29CCJF8x3I8MIoLh L3kopATOcgNjQ6kUJ39jcyi8PI/gsL9aT7zLgpSMdeQ1+FRa0w8hZxM8LgKskYvMx8rF 5HfCD56fGJauT9J5NFAkC6/rmfaB6923x5c6YtJWifQ5GApJMeDTr+/DaDeU/BC/EwVt eKDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=gVoE4cOUuOvvDi2DF+IDKSMyqTjYt7iW9iqwWV1UAa0=; b=gJhaZHWKe3qD4cVIhLrLnrkFoXfRamJOpF8Az/Kc2tOOc2ECa09rr/O/WQIgVrTZi5 nB9VNm7IAYe+VkWqhLBQth9+S1P5wbgLD4V8DLsjuMiy2afCN/Fxj1eHfuUu+LFYms9Y 71xGhUlolv8i7Dwwk4Rpo5tLmhlhpSQUY77qDoPHd/gTRjqTtcbO1pdISkqDve3ZqQaX 3nuChh2eEE/mezjHCE1eZkoAw+cxQNpBKgm5T547BUcGrUZZjV60J/F7+E0tO1aWR3dq mNZS4QezqH2/GKAyIY2qoOJ6+h0qP7zzd4U2U2VxebzrZbu0hFjCC19XEkHwzdfWlZQN tcuw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d4-v6si13510717plr.598.2018.03.07.15.33.04; Wed, 07 Mar 2018 15:33:19 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934457AbeCGXbd (ORCPT + 99 others); Wed, 7 Mar 2018 18:31:33 -0500 Received: from wtarreau.pck.nerim.net ([62.212.114.60]:41230 "EHLO 1wt.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934158AbeCGXbb (ORCPT ); Wed, 7 Mar 2018 18:31:31 -0500 Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id w27NREIo010195; Thu, 8 Mar 2018 00:27:14 +0100 Date: Thu, 8 Mar 2018 00:27:14 +0100 From: Willy Tarreau To: Boris Brezillon Cc: Pavel Machek , David Woodhouse , Greg KH , Steve deRosier , Richard Weinberger , Boris Brezillon , dedekind1@gmail.com, tharvey@gateworks.com, linux-kernel@vger.kernel.org, stable@vger.kernel.org, marek.vasut@gmail.com, linux-mtd@lists.infradead.org, cyrille.pitchen@wedev4u.fr, computersforpeace@gmail.com Subject: Re: [PATCH] ubi: Reject MLC NAND Message-ID: <20180307232714.GA10178@1wt.eu> References: <20180303104554.5958-1-richard@nod.at> <20180306231805.GA28183@amd> <6772577.AmT7QaWTNU@blindfold> <20180307214342.GA9852@amd> <1520460673.31298.136.camel@infradead.org> <20180307221733.GE10438@amd> <20180307233057.54bd35c3@bbrezillon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180307233057.54bd35c3@bbrezillon> User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Boris, On Wed, Mar 07, 2018 at 11:30:57PM +0100, Boris Brezillon wrote: > I have one simple question: did you ever play with MLC NANDs or are you > just trolling? If you had, like Richard and I did when working on MLC > support, I'm pretty sure you wouldn't play this "don't backport to > stable" card. Just adding my two cents here, I've always had stability issues with ubifs on NAND and I never knew what type of NAND I've had in these devices (eg: Iomega Iconnect with 256 MB NAND IIRC), so maybe this has never been relevant, maybe it has been, I don't know. However, as a stable maintainer I also know that we want to encourage people to always keep their kernels up to date with latest fixes, and that if there is the slightest risk that a loss of functionality makes people revert and stick to an older, working version, keeping their bugs forever, it's twice as worse, because : - they still run on the bug you wanted to fix - they are now exposed to all bugs fixed later. And we all do this as users, thinking "I'll bisect and report tomorrow" and priorities change, let's be honnest. Thus I think that if you are absolutely certain that it's impossible that people are accidently using this combination, it's probably fine, but if people are using it, you're just displacing the burden on the stable team who will have to explain to each and every user complaining "my system stopped booting after an upgrade to 4.x.y". A big red alert polluting the logs and console every minute, and a pause at boot saying "your NAND, your data and all your kids photos will die soon if you don't switch to another FS" is more productive as users will be less tempted to blindly revert and will at least ask what the problem is and what their solutions are. There's nothing more frustrating than a regression in a stable branch, even for something that was not supposed to work but did by accident. > I wouldn't say "work by mistake" but "seems to work at first but in the > end breaks", so definitely a candidate for -stable IMO. Well, removing support definitely makes the end closer and possibly even prevents the user from recovering their data. I know that data loss is terrible, but data confiscation is similar from the user's point of view. Users don't know the technical details so they will do all things we often consider stupid or impossible, but when warned they know that the risk is on their side and they cannot put the fault at anybody anymore. It tends to work better. Just my two cents, Willy