Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3334631imu; Sun, 11 Nov 2018 12:37:00 -0800 (PST) X-Google-Smtp-Source: AJdET5cvav+6VpspMsngPT7BoBYxbVP+cb8MVFuinkRw1yaMlWsYkbTMCledbMJM+E+eVfgtQVFX X-Received: by 2002:a63:2ad4:: with SMTP id q203-v6mr14738889pgq.356.1541968620210; Sun, 11 Nov 2018 12:37:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541968620; cv=none; d=google.com; s=arc-20160816; b=dRKUw3yZ8rTZZif5Ge2zhgYeOp2KIM+jYuq1/rCcwhwqOvCeerMBbobS1T2m0+fUMe FFeDmIHdtoepcXQjAidV0UatHO5IIkIBzPjaEWmgEIDruMoOZfAUFxXnfYCCFCnlkjS3 Bb0N8I7q4qLd3SRqRunYSzvXHWaTNf93pUmigEanQClS8q9JMypw2ww2Q4qtNPH1u2MW BQOruUn8ayFR6SaZvnGE1tCC36LoVPCGGWxSfPBDlTm4ezh6fj9nMHdpSIXwzE2iJoI3 G2wYeh3Qya0GavYQalS3vcjoIR5VYduHVC+nhi3XEZc4tJmpuAnOSL1bgI7otzqhokZp llBQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition; bh=O5cb4rrQWb0XjHaXAHtraZ3HAZTGsNV6aCfvltv6WgM=; b=D6Wz9tb1IPGeau0U7bnrY4hSRmv0V/eucP3XAAfWEpCY46DL6criu5kypJcgfYxBBu w7kv/DxRhc/tXoIB8oBWPEGw0B1g/vPpLQ8sZfg5GJR6Wju7KvJdEMjojEC3cTV024Xc wuU7ivqS76x3MWZHjUbrabDfqx0V4lU6hRI7Ohb6fukQ8Bj1X8S/1Y7Zn4rfZ76bpdiF iYvQJ4uWoicF0aC7mATrEm3xa9X+IFLXn1SUiUIC5Y8H4Q4Wf6hRDBYLua4f6A8b/lt3 zQsaCD1Iqb8KQuzcPGoAmw/q+OIhXD5poj3zHZ4dF+g6wvrQho5UeLpDin3Sz1T6SpmM 98qw== 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 b12-v6si15005496plr.175.2018.11.11.12.36.45; Sun, 11 Nov 2018 12:37:00 -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 S1730159AbeKLFsM (ORCPT + 99 others); Mon, 12 Nov 2018 00:48:12 -0500 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:49660 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730051AbeKLFsK (ORCPT ); Mon, 12 Nov 2018 00:48:10 -0500 Received: from [192.168.4.242] (helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gLvsW-0000lK-CU; Sun, 11 Nov 2018 19:58:40 +0000 Received: from ben by deadeye with local (Exim 4.91) (envelope-from ) id 1gLvsT-0001bh-Db; Sun, 11 Nov 2018 19:58:37 +0000 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, "Boris Brezillon" , "Joakim Tjernlund" Date: Sun, 11 Nov 2018 19:49:05 +0000 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) Subject: [PATCH 3.16 175/366] mtd: cfi_cmdset_0002: Fix unlocking requests crossing a chip boudary In-Reply-To: X-SA-Exim-Connect-IP: 192.168.4.242 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.61-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Joakim Tjernlund commit 0cd8116f172eed018907303dbff5c112690eeb91 upstream. The "sector is in requested range" test used to determine whether sectors should be re-locked or not is done on a variable that is reset everytime we cross a chip boundary, which can lead to some blocks being re-locked while the caller expect them to be unlocked. Fix the check to make sure this cannot happen. Fixes: 1648eaaa1575 ("mtd: cfi_cmdset_0002: Support Persistent Protection Bits (PPB) locking") Signed-off-by: Joakim Tjernlund Signed-off-by: Boris Brezillon Signed-off-by: Ben Hutchings --- drivers/mtd/chips/cfi_cmdset_0002.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/mtd/chips/cfi_cmdset_0002.c +++ b/drivers/mtd/chips/cfi_cmdset_0002.c @@ -2340,7 +2340,7 @@ static int __maybe_unused cfi_ppb_unlock * sectors shall be unlocked, so lets keep their locking * status at "unlocked" (locked=0) for the final re-locking. */ - if ((adr < ofs) || (adr >= (ofs + len))) { + if ((offset < ofs) || (offset >= (ofs + len))) { sect[sectors].chip = &cfi->chips[chipnum]; sect[sectors].adr = adr; sect[sectors].locked = do_ppb_xxlock(