Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38;
From:   Martin Kurbanov <mmkurbanov@salutedevices.com>
To:     David Woodhouse <dwmw2@infradead.org>,
        Richard Weinberger <richard@nod.at>,
        Christian Brauner <brauner@kernel.org>,
        Dave Chinner <dchinner@redhat.com>, Yu Zhe <yuzhe@nfschina.com>
CC:     <linux-kernel@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
        <kernel@sberdevices.ru>,
        Martin Kurbanov <mmkurbanov@salutedevices.com>
Subject: [PATCH v1 0/2] jffs2: make cleanmarker support option
Date:   Thu, 19 Oct 2023 10:38:36 +0300
Message-ID: <20231019073838.17586-1-mmkurbanov@salutedevices.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain
Precedence: bulk

This patchset support for disable cleanmarker option. This is useful on
some NAND devices which entire OOB area is protected by ECC. Problem
fires when JFFS2 driver writes cleanmarker to some page and later it
tries to write to this page - write will be done successfully, but after
that such page becomes unreadable due to invalid ECC codes. This occurs
because the second write necessitates an update to ECC, but it is
impossible to do it correctly without block erase.

Martin Kurbanov (2):
  jffs2: introduce jffs2_nandflash()
  jffs2: make cleanmarker support option

 fs/jffs2/Kconfig    | 10 ++++++++++
 fs/jffs2/erase.c    |  2 +-
 fs/jffs2/fs.c       |  4 ++--
 fs/jffs2/os-linux.h |  7 ++++++-
 fs/jffs2/scan.c     |  2 +-
 5 files changed, 20 insertions(+), 5 deletions(-)

-- 
2.40.0