From: Pratyush Yadav <pratyush@kernel.org>
To: Amit Kumar Mahapatra <amit.kumar-mahapatra@amd.com>
Cc: <tudor.ambarus@linaro.org>, <pratyush@kernel.org>,
<mwalle@kernel.org>, <miquel.raynal@bootlin.com>,
<richard@nod.at>, <vigneshr@ti.com>, <csokas.bence@prolan.hu>,
<linux-mtd@lists.infradead.org>, <git@amd.com>,
<amitrkcian2002@gmail.com>
Subject: Re: [PATCH] mtd: spi-nor: sst: Fix SST write failure
Date: Mon, 17 Feb 2025 14:21:09 +0000 [thread overview]
Message-ID: <mafs0cyfgmz3e.fsf@kernel.org> (raw)
In-Reply-To: <20250213054546.2078121-1-amit.kumar-mahapatra@amd.com> (Amit Kumar Mahapatra's message of "Thu, 13 Feb 2025 11:15:46 +0530")
On Thu, Feb 13 2025, Amit Kumar Mahapatra wrote:
> 'commit 18bcb4aa54ea ("mtd: spi-nor: sst: Factor out common write operation
> to `sst_nor_write_data()`")' introduced a bug where only one byte of data
> is written, regardless of the number of bytes passed to
> sst_nor_write_data(), causing a kernel crash during the write operation.
> Ensure the correct number of bytes are written as passed to
> sst_nor_write_data().
>
> Call trace:
> [ 57.400180] ------------[ cut here ]------------
> [ 57.404842] While writing 2 byte written 1 bytes
> [ 57.409493] WARNING: CPU: 0 PID: 737 at drivers/mtd/spi-nor/sst.c:187 sst_nor_write_data+0x6c/0x74
> [ 57.418464] Modules linked in:
> [ 57.421517] CPU: 0 UID: 0 PID: 737 Comm: mtd_debug Not tainted 6.12.0-g5ad04afd91f9 #30
> [ 57.429517] Hardware name: Xilinx Versal A2197 Processor board revA - x-prc-02 revA (DT)
> [ 57.437600] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 57.444557] pc : sst_nor_write_data+0x6c/0x74
> [ 57.448911] lr : sst_nor_write_data+0x6c/0x74
> [ 57.453264] sp : ffff80008232bb40
> [ 57.456570] x29: ffff80008232bb40 x28: 0000000000010000 x27: 0000000000000001
> [ 57.463708] x26: 000000000000ffff x25: 0000000000000000 x24: 0000000000000000
> [ 57.470843] x23: 0000000000010000 x22: ffff80008232bbf0 x21: ffff000816230000
> [ 57.477978] x20: ffff0008056c0080 x19: 0000000000000002 x18: 0000000000000006
> [ 57.485112] x17: 0000000000000000 x16: 0000000000000000 x15: ffff80008232b580
> [ 57.492246] x14: 0000000000000000 x13: ffff8000816d1530 x12: 00000000000004a4
> [ 57.499380] x11: 000000000000018c x10: ffff8000816fd530 x9 : ffff8000816d1530
> [ 57.506515] x8 : 00000000fffff7ff x7 : ffff8000816fd530 x6 : 0000000000000001
> [ 57.513649] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
> [ 57.520782] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0008049b0000
> [ 57.527916] Call trace:
> [ 57.530354] sst_nor_write_data+0x6c/0x74
> [ 57.534361] sst_nor_write+0xb4/0x18c
> [ 57.538019] mtd_write_oob_std+0x7c/0x88
> [ 57.541941] mtd_write_oob+0x70/0xbc
> [ 57.545511] mtd_write+0x68/0xa8
> [ 57.548733] mtdchar_write+0x10c/0x290
> [ 57.552477] vfs_write+0xb4/0x3a8
> [ 57.555791] ksys_write+0x74/0x10c
> [ 57.559189] __arm64_sys_write+0x1c/0x28
> [ 57.563109] invoke_syscall+0x54/0x11c
> [ 57.566856] el0_svc_common.constprop.0+0xc0/0xe0
> [ 57.571557] do_el0_svc+0x1c/0x28
> [ 57.574868] el0_svc+0x30/0xcc
> [ 57.577921] el0t_64_sync_handler+0x120/0x12c
> [ 57.582276] el0t_64_sync+0x190/0x194
> [ 57.585933] ---[ end trace 0000000000000000 ]---
>
> Fixes: 18bcb4aa54ea ("mtd: spi-nor: sst: Factor out common write operation to `sst_nor_write_data()`")
> Signed-off-by: Amit Kumar Mahapatra <amit.kumar-mahapatra@amd.com>
Applied to spi-nor/fixes with Cc: stable@vger.kernel.org added.
> ---
> BRANCH: mtd/next
> ---
> drivers/mtd/spi-nor/sst.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/spi-nor/sst.c b/drivers/mtd/spi-nor/sst.c
> index b5ad7118c49a..175211fe6a5e 100644
> --- a/drivers/mtd/spi-nor/sst.c
> +++ b/drivers/mtd/spi-nor/sst.c
> @@ -174,7 +174,7 @@ static int sst_nor_write_data(struct spi_nor *nor, loff_t to, size_t len,
> int ret;
>
> nor->program_opcode = op;
> - ret = spi_nor_write_data(nor, to, 1, buf);
> + ret = spi_nor_write_data(nor, to, len, buf);
> if (ret < 0)
> return ret;
> WARN(ret != len, "While writing %zu byte written %i bytes\n", len, ret);
--
Regards,
Pratyush Yadav
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2025-02-17 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 5:45 [PATCH] mtd: spi-nor: sst: Fix SST write failure Amit Kumar Mahapatra
2025-02-13 7:47 ` Pratyush Yadav
2025-02-13 8:09 ` Tudor Ambarus
2025-02-13 12:48 ` Csókás Bence
2025-02-17 14:21 ` Pratyush Yadav [this message]
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=mafs0cyfgmz3e.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=amit.kumar-mahapatra@amd.com \
--cc=amitrkcian2002@gmail.com \
--cc=csokas.bence@prolan.hu \
--cc=git@amd.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.