From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Joakim Tjernlund <joakim.tjernlund@infinera.com>
Cc: "linux-mtd @ lists . infradead . org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 1/2] mtd: cfi_cmdset_0002: fix SEGV unlocking multiple chips
Date: Tue, 5 Jun 2018 17:02:13 +0200 [thread overview]
Message-ID: <20180605170213.7c937bf4@bbrezillon> (raw)
In-Reply-To: <20180605140710.8624-1-joakim.tjernlund@infinera.com>
On Tue, 5 Jun 2018 16:07:09 +0200
Joakim Tjernlund <joakim.tjernlund@infinera.com> wrote:
> cfi_ppb_unlock() tries to relock all sectors that was locked before
> unlocking the whole chip.
> This locking used the chip start address + the FULL offset from the
> first flash chip, thereby forming an illegal address. Correct by using
> the chip offset(adr).
>
> In addition, do_ppb_xxlock() failed to add chip->start when
> quering for lock status(and chip_ready test),
> which caused false status reports.
> Fix by adding adr += chip->start and adjust call sites accordingly.
>
> Fixes: 1648eaaa1575e
Fixes: 1648eaaa1575 ("mtd: cfi_cmdset_0002: Support Persistent Protection Bits (PPB) locking")
And you probably want to add
Cc: stable@vger.kernel.org
> Signed-off-by: Joakim Tjernlund <joakim.tjernlund@infinera.com>
> ---
> drivers/mtd/chips/cfi_cmdset_0002.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/mtd/chips/cfi_cmdset_0002.c b/drivers/mtd/chips/cfi_cmdset_0002.c
> index 5e526aec66f0..c74c53b886be 100644
> --- a/drivers/mtd/chips/cfi_cmdset_0002.c
> +++ b/drivers/mtd/chips/cfi_cmdset_0002.c
> @@ -2535,7 +2535,7 @@ static int cfi_atmel_unlock(struct mtd_info *mtd, loff_t ofs, uint64_t len)
>
> struct ppb_lock {
> struct flchip *chip;
> - loff_t offset;
> + unsigned long adr;
> int locked;
> };
>
> @@ -2553,8 +2553,9 @@ static int __maybe_unused do_ppb_xxlock(struct map_info *map,
> unsigned long timeo;
> int ret;
>
> + adr += chip->start;
> mutex_lock(&chip->mutex);
> - ret = get_chip(map, chip, adr + chip->start, FL_LOCKING);
> + ret = get_chip(map, chip, adr, FL_LOCKING);
> if (ret) {
> mutex_unlock(&chip->mutex);
> return ret;
> @@ -2572,8 +2573,8 @@ static int __maybe_unused do_ppb_xxlock(struct map_info *map,
>
> if (thunk == DO_XXLOCK_ONEBLOCK_LOCK) {
> chip->state = FL_LOCKING;
> - map_write(map, CMD(0xA0), chip->start + adr);
> - map_write(map, CMD(0x00), chip->start + adr);
> + map_write(map, CMD(0xA0), adr);
> + map_write(map, CMD(0x00), adr);
> } else if (thunk == DO_XXLOCK_ONEBLOCK_UNLOCK) {
> /*
> * Unlocking of one specific sector is not supported, so we
> @@ -2611,7 +2612,7 @@ static int __maybe_unused do_ppb_xxlock(struct map_info *map,
> map_write(map, CMD(0x00), chip->start);
>
> chip->state = FL_READY;
> - put_chip(map, chip, adr + chip->start);
> + put_chip(map, chip, adr);
> mutex_unlock(&chip->mutex);
>
> return ret;
> @@ -2670,7 +2671,7 @@ static int __maybe_unused cfi_ppb_unlock(struct mtd_info *mtd, loff_t ofs,
> */
> if ((adr < ofs) || (adr >= (ofs + len))) {
> sect[sectors].chip = &cfi->chips[chipnum];
> - sect[sectors].offset = offset;
> + sect[sectors].adr = adr;
> sect[sectors].locked = do_ppb_xxlock(
> map, &cfi->chips[chipnum], adr, 0,
> DO_XXLOCK_ONEBLOCK_GETLOCK);
> @@ -2686,7 +2687,6 @@ static int __maybe_unused cfi_ppb_unlock(struct mtd_info *mtd, loff_t ofs,
> if (adr >> cfi->chipshift) {
> adr = 0;
> chipnum++;
> -
> if (chipnum >= cfi->numchips)
> break;
> }
> @@ -2714,7 +2714,7 @@ static int __maybe_unused cfi_ppb_unlock(struct mtd_info *mtd, loff_t ofs,
> */
> for (i = 0; i < sectors; i++) {
> if (sect[i].locked)
> - do_ppb_xxlock(map, sect[i].chip, sect[i].offset, 0,
> + do_ppb_xxlock(map, sect[i].chip, sect[i].adr, 0,
> DO_XXLOCK_ONEBLOCK_LOCK);
> }
>
next prev parent reply other threads:[~2018-06-05 15:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 14:07 [PATCH 1/2] mtd: cfi_cmdset_0002: fix SEGV unlocking multiple chips Joakim Tjernlund
2018-06-05 14:07 ` [PATCH 2/2] mtd: cfi_cmdset_0002: Avoid point less unlocking/locking Joakim Tjernlund
2018-06-05 15:14 ` Boris Brezillon
2018-06-05 16:57 ` Joakim Tjernlund
2018-06-06 10:15 ` Joakim Tjernlund
2018-06-19 17:23 ` Joakim Tjernlund
2018-06-05 15:02 ` Boris Brezillon [this message]
2018-06-05 15:26 ` [PATCH 1/2] mtd: cfi_cmdset_0002: fix SEGV unlocking multiple chips Boris Brezillon
2018-06-05 15:33 ` Joakim Tjernlund
2018-06-06 10:13 ` [PATCH v2 1/4] mtd: cfi_cmdset_0002: Use right chip in do_ppb_xxlock() Joakim Tjernlund
2018-06-06 10:13 ` [PATCH v2 2/4] mtd: cfi_cmdset_0002: fix SEGV unlocking multiple chips Joakim Tjernlund
2018-06-20 9:06 ` Boris Brezillon
2018-06-06 10:13 ` [PATCH v2 3/4] mtd: cfi_cmdset_0002: Avoid point less unlocking/locking Joakim Tjernlund
2018-06-20 9:14 ` Boris Brezillon
2018-06-20 11:10 ` Joakim Tjernlund
2018-06-20 11:54 ` Boris Brezillon
2018-06-06 10:13 ` [PATCH v2 4/4] mtd: cfi_cmdset_0002: Avoid walking all chips when unlocking Joakim Tjernlund
2018-06-20 9:25 ` Boris Brezillon
2018-06-20 11:10 ` Joakim Tjernlund
2018-06-20 12:19 ` Boris Brezillon
2018-06-20 15:07 ` Joakim Tjernlund
2018-06-20 9:03 ` [PATCH v2 1/4] mtd: cfi_cmdset_0002: Use right chip in do_ppb_xxlock() Boris Brezillon
2018-06-20 11:10 ` Joakim Tjernlund
2018-06-22 11:35 ` Boris Brezillon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180605170213.7c937bf4@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=joakim.tjernlund@infinera.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).