Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp1520512imd; Thu, 1 Nov 2018 17:38:44 -0700 (PDT) X-Google-Smtp-Source: AJdET5dTwoOnS9z2RtIxGcL29I9XaLgicygEkRl78T2vrIluegdIZaIATtWRgnE0QaT3xrwVIFoB X-Received: by 2002:a17:902:15a8:: with SMTP id m37-v6mr9660752pla.256.1541119124132; Thu, 01 Nov 2018 17:38:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541119124; cv=none; d=google.com; s=arc-20160816; b=uGSdCx7DzVEgKlJQHubTRnltIJ3h8MP4ckZPkcUhV86UFv6IpN0jIxGKHODenfjHj4 XISMilTaJ2RMXR0Cdty5V6BU1OqSPUYfQ4cmqv6+oAmbxpujAoN8Qgr72njaEU0KgM12 kiium4e4lHJZbP4nUQodlKxY/NX2dYplEPwkEX+WgUNe3puz9uwSs3dsbB9GDLpadKyL wmmEfa3OeL+c3bc1I46qusrZ2EOcI2oXcVtC23ubSnne737dmRIibaaYN2XbxDkAbazP um/zMe1QU7AAXg8tnznCnfOoIeEBiK586yU59X5bWOWcm/2C9DXG809IBH9xovhEOugA 5kPw== 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; bh=B+At2eKjrkC4u1xOk9EsI6022IUZeJErZEkD8aHtKNI=; b=u0/GokXS4Z+JTVTC4BXUvF2d3u5gWxvIA1oeUHzmmXt7ZeUGwdO8jiZWPFHyyKVDzg VlAFO/xOPA6iBjHqDBhka/6HigVrZg8v23kHmKPWw6NhuMilI41u1lioOdNVeP6D227K 0z5WvOyOSr+W3Trrnt4tZbxxhEO8+DAf2Mr2TJhdzaUp5GXK1jxXaps4n+i7rds2PC/s g5d6W9j93ZHOpVVUd7u8rSMTZY46I+bINAgludD9qr7NsMiVwIMmTnG01J6yN78tZQxD KKsswaYV2JHYxU6Pq4cQpWUlyAhOM8KuEpYsKQ28FtBli7vn52fXxlxDuLfK49eZgZEL 50Wg== 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 3-v6si20271166pll.361.2018.11.01.17.38.29; Thu, 01 Nov 2018 17:38:44 -0700 (PDT) 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 S1728315AbeKBJmG (ORCPT + 99 others); Fri, 2 Nov 2018 05:42:06 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:58678 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728231AbeKBJmF (ORCPT ); Fri, 2 Nov 2018 05:42:05 -0400 Received: from viro by ZenIV.linux.org.uk with local (Exim 4.90_1 #2 (Red Hat Linux)) id 1gINQ2-0006MQ-Am; Fri, 02 Nov 2018 00:34:34 +0000 Date: Fri, 2 Nov 2018 00:34:34 +0000 From: Al Viro To: Daniel Walker Cc: Nikunj Kela , David Woodhouse , xe-linux-external@cisco.com, Rod Whitby , linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Make JFFS2 endianness configurable Message-ID: <20181102003434.GW32577@ZenIV.linux.org.uk> References: <20181101225603.17806-1-nkela@cisco.com> <20181102000236.rqho7txtb7gv543t@zorba> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181102000236.rqho7txtb7gv543t@zorba> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 01, 2018 at 05:02:36PM -0700, Daniel Walker wrote: > > > > On Thu, Nov 01, 2018 at 03:56:03PM -0700, Nikunj Kela wrote: > > This patch allows the endianness of the JFSS2 filesystem to be > > specified by config options. > > > > It defaults to native-endian (the previously hard-coded option). > > > > Some architectures benefit from having a single known endianness > > of JFFS2 filesystem (for data, not executables) independent of the > > endianness of the processor (ARM processors can be switched to either > > endianness at run-time). > > > > > The description is pretty sad .. We have a product which we released that uses > JFFS2, and that product was release with a kernel in one endianness. Then later > on we decided to change the endianness and now we're stuck with a JFFS2 > partition that has the wrong endiannes, in a released product. This patch allows > us to set the endianness to something different from the architecture setting. > > So there a significant use case for the change, at least for Cisco. FWIW, can't we detect it at mount time, as e.g. UFS does?