From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:48140 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751063AbdK1ImG (ORCPT
        <rfc822;stable@vger.kernel.org>); Tue, 28 Nov 2017 03:42:06 -0500
Date: Tue, 28 Nov 2017 09:42:09 +0100
From: Greg KH <gregkh@linuxfoundation.org>
To: motobud@gmail.com
Cc: boris.brezillon@free-electrons.com, stable@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: Fix writing mtdoops to nand flash
Message-ID: <20171128084209.GF9413@kroah.com>
References: <20171128055914.25355-1-motobud@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171128055914.25355-1-motobud@gmail.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Mon, Nov 27, 2017 at 11:59:14PM -0600, motobud@gmail.com wrote:
> From: Brent Taylor <motobud@gmail.com>
> 
> commit 30863e38ebeb500a31cecee8096fb5002677dd9b upstream.
> 
> When mtdoops calls mtd_panic_write(), it eventually calls
> panic_nand_write() in nand_base.c. In order to properly wait for the
> nand chip to be ready in panic_nand_wait(), the chip must first be
> selected.
> 
> When using the atmel nand flash controller, a panic would occur due to
> a NULL pointer exception.
> 
> Fixes: 2af7c6539931 ("mtd: Add panic_write for NAND flashes")
> Cc: <stable@vger.kernel.org> # 4.4.x

This does not apply to the 4.4.x tree at all, only 3.18.x.  Can you
provide a backport for 4.4.x as well?

thanks,

greg k-h