Received: by 10.223.185.116 with SMTP id b49csp5569449wrg; Wed, 7 Mar 2018 14:10:48 -0800 (PST) X-Google-Smtp-Source: AG47ELv3ZRibTW9X/8QFZ8AEDWZOQWoauZpUS3faGa/c/5+4rBulDFuKB2hPV8yH2Br8izT9ubi7 X-Received: by 2002:a17:902:7404:: with SMTP id g4-v6mr21631913pll.235.1520460647941; Wed, 07 Mar 2018 14:10:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520460647; cv=none; d=google.com; s=arc-20160816; b=y0/XlBsB78YHcGMy936BJpbjldJzUXWNDqISPcBs1YWow4CKDQvek26A4EVVqp4ozD iTn+rXY9RTWNmOX0B6vJuAfVwujXoFhRigSkJ3+U5FA4kVfVPB5p277lUZapf+Fg2/tS IFfMzw6pCnjF7yN/S7ZJ/UTD/+yRkPVWQXQu6MuNDLoRBx6qSSMHz4dBac4ki3seeFE9 t9x6a1GbG83HPYvCIFZYppvUDSf0RbYpisY03afiODFsXX/sodD+vYIst8USrxssXk3k ajQNd0+BQzRT1p/QdSBLtsw347Hf1nC7qsc56u//vUktX143rQKTda0BsWYzfaG/uHDk CK/w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:references:in-reply-to:mime-version :dkim-signature:arc-authentication-results; bh=QIblE2sJebzLiaNBcnbDE/Dac3WSQc2x1Z/BgTAj+Ek=; b=tHpQFwVqqy+ye+SEO4VIVxQ3VFfrfDvKAq0ZQCpQIHymXvEf82XFwSAC0u2SXL926C NaGU/REk8cY7nhVt4cqLXAQvzqD/shfGjWBqKTiOitLNPdbtbgbpRvD05YiZgN8MO2qB Hg5KngJ75nXIyO7MJhncJ1hRg3yi8kxSHrEYIrPXYA3umW9B+5+z2LGDIihBwsxLb4jV w4gsnPxZIwRsrh7J+7tS3u30/h8iAwRQvIFe0fATEcgXrrDsr1UfDIVtmP6ZnhaEbwtW 4DvaH4adxgdugdfC0zyOJGpSKHrrLS81VS/3asX1VRaPIZ5pPXHfDf0iYB1898GMpAYL bweg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=bT+SDRUf; 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; dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e87si14613396pfk.322.2018.03.07.14.10.33; Wed, 07 Mar 2018 14:10:47 -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; dkim=fail header.i=@gmail.com header.s=20161025 header.b=bT+SDRUf; 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; dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754903AbeCGWJH (ORCPT + 99 others); Wed, 7 Mar 2018 17:09:07 -0500 Received: from mail-wr0-f194.google.com ([209.85.128.194]:34834 "EHLO mail-wr0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754547AbeCGWJG (ORCPT ); Wed, 7 Mar 2018 17:09:06 -0500 Received: by mail-wr0-f194.google.com with SMTP id l43so3732643wrc.2; Wed, 07 Mar 2018 14:09:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=QIblE2sJebzLiaNBcnbDE/Dac3WSQc2x1Z/BgTAj+Ek=; b=bT+SDRUfmIL0TuF96sVEKDw5oalAqrS1BGqMKztRAJmVuA8cvsvi1vNhYFS5W5g2Rg 9GdLhbPslYXv1D5pfs2417SSsgQnwr6430vInsGvmoCRjPFJngliTCO4N9/jGFT7hYDH WT2bx+bhr5VN2rbXAk0J+EkA0Sl/jhj9K3Q5O+CvUqrmdtL+vF3g9OaA/4mui5kcXizY zcXXO45LS7+JHHBaWXKbGOE70fmQrCokR0IavuiniwRMWZ1IgLfW016a1+Y0fmpvDRIt 67WZuAPMSBYjNikShjwzpHV9eOKnA2u+I+10IIOPbEhXFJ+0l0sFmZtn5FG0QhZSJle3 vTIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=QIblE2sJebzLiaNBcnbDE/Dac3WSQc2x1Z/BgTAj+Ek=; b=cHN5gEJmMaBXxhT4O1eSovMmutnHoW+c7sg+JQQRdCzgtBPue0Schcg93s5baDiqyO jkMItwKdt+2tssIgBYLuJN+j9v7SHCyMoC0EzEICI7PZGouLas8Pfo5Dq1vhqXI47HfC G1VO9tRiXD9Kd67KPozsY657YJoOdXt6iUgVbVI1HvH/XP54m7LsC2sr7rcKrOYgSMil jWe+Px7nyw9vrRjGJDlJeYaPRzJV8V64Ix/+jC9+T6iOPNHzmTxzDzjiZ3hVCJ7Bu1R0 VxDA+UlEuaS60A6pqsZOlcCRPXXVZvo7TuRK0qHgoLmZcmtbOABGZe6SUWbeS+AK/RHc GEyQ== X-Gm-Message-State: APf1xPDPFYhh/l+QXkzeF60QEnZkh+WTB5EELu4YeArXAn66xzuus97g Ej1T2fPBvjvUwCNHPU8uHIaviNB8RBKkqRb5uhYvc1tO X-Received: by 10.223.164.153 with SMTP id g25mr21693048wrb.79.1520460545077; Wed, 07 Mar 2018 14:09:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.176.139 with HTTP; Wed, 7 Mar 2018 14:08:24 -0800 (PST) In-Reply-To: <20180307214342.GA9852@amd> References: <20180303104554.5958-1-richard@nod.at> <20180306231805.GA28183@amd> <6772577.AmT7QaWTNU@blindfold> <20180307214342.GA9852@amd> From: Steve deRosier Date: Wed, 7 Mar 2018 14:08:24 -0800 X-Google-Sender-Auth: eEL9zHE3hDAofD3pO-_LE632GWo Message-ID: Subject: Re: [PATCH] ubi: Reject MLC NAND To: Pavel Machek Cc: 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, dwmw2@infradead.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Pavel, On Wed, Mar 7, 2018 at 1:43 PM, Pavel Machek wrote: > On Wed 2018-03-07 09:01:16, Richard Weinberger wrote: >> Pavel, >> >> Am Mittwoch, 7. M=C3=A4rz 2018, 00:18:05 CET schrieb Pavel Machek: >> > On Sat 2018-03-03 11:45:54, Richard Weinberger wrote: >> > > While UBI and UBIFS seem to work at first sight with MLC NAND, you w= ill >> > > most likely lose all your data upon a power-cut or due to read/write >> > > disturb. >> > > In order to protect users from bad surprises, refuse to attach to ML= C >> > > NAND. >> > > >> > > Cc: stable@vger.kernel.org >> > >> > That sounds like _really_ bad idea for stable. All it does is it >> > removes support for hardware that somehow works. >> >> MLC is not supported and does not work. Full stop. >> If someone manages to get it somehow work, either with hardware or softw= are >> hacks they are on their own. >> Having it in stable is the only chance we have to get it into vendor >> kernels. > > Can you show how it meets the stable kernel criteria? They are > documented in tree. This should not be in stable. > > And I'd like to see changelog improved. Real reason MLC is not > supported is upper/lower page parts on MLC. And real fix to work with > bigger pages in UBI. > To clarify one thing: the reason for this is MLC has actually never been supported, nor worked properly. The fact that it kinda worked was incidental and the cause of major problems for people due to that not being clear. This patch only makes it explicit and avoids people mistakenly trying to use UBIFS on MLC flash and risking their data and products. To me, that's what's important. This is an important patch, even if all it does is keep people from loosing data. It also changes the conversation from "I have a corrupted UBIFS device, BTW it's on MLC..." to "What can we do to get UBIFS to work on MLC". I don't know what the stable criteria is with re: to this patch. But what I do know is if it doesn't go back into the various stables, there will be manufacturers who will continue to try to use UBIFS on MLC in ignorance for the next several years until the current stable kernels EOL, despite there being a known patch that would make it immediately obvious they shouldn't. Thanks, - Steve