All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	linux-mtd@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH] mtd: devices: m25p80: Make the buffer passed in op is DMA-able
Date: Mon, 17 Sep 2018 16:22:37 +0200	[thread overview]
Message-ID: <20180917162237.49e6889f@bbrezillon> (raw)
In-Reply-To: <239bb1a4-c986-0f5e-61b9-a08f54947bfe@linux.intel.com>

On Mon, 17 Sep 2018 17:13:32 +0300
Jarkko Nikula <jarkko.nikula@linux.intel.com> wrote:

> On 09/17/2018 04:36 PM, Boris Brezillon wrote:
> > As documented in spi-mem.h, spi_mem_op->data.buf.{in,out} must be
> > DMA-able, and commit 4120f8d158ef ("mtd: spi-nor: Use the spi_mem_xx()
> > API") failed to follow this rule as buffers passed to  
> > ->{read,write}_reg() are usually placed on the stack.  
> > 
> > Fix that by allocating a scratch buffer and copying the data in there
> > before passing it to the spi-mem layer.
> > 
> > Fixes: 4120f8d158ef ("mtd: spi-nor: Use the spi_mem_xx() API")
> > Reported-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
> > ---
> > Note that the ->{read,write}() path is still buggy since nothing
> > guarantees that buffers passed by the MTD layer to the SPI NOR layer
> > are DMA-able, but this is a long-standing issue which we'll have to
> > address at the spi-nor level (this layer can choose the bounce buffer
> > size based on nor->page_size).
> > ---
> >   drivers/mtd/devices/m25p80.c | 24 +++++++++++++++++++++---
> >   1 file changed, 21 insertions(+), 3 deletions(-)
> > 
> > diff --git a/drivers/mtd/devices/m25p80.c b/drivers/mtd/devices/m25p80.c
> > index cbfafc453274..3b7fafa4bbd6 100644
> > --- a/drivers/mtd/devices/m25p80.c
> > +++ b/drivers/mtd/devices/m25p80.c
> > @@ -39,14 +39,22 @@ static int m25p80_read_reg(struct spi_nor *nor, u8 code, u8 *val, int len)
> >   	struct spi_mem_op op = SPI_MEM_OP(SPI_MEM_OP_CMD(code, 1),
> >   					  SPI_MEM_OP_NO_ADDR,
> >   					  SPI_MEM_OP_NO_DUMMY,
> > -					  SPI_MEM_OP_DATA_IN(len, val, 1));
> > +					  SPI_MEM_OP_DATA_IN(len, NULL, 1));
> > +	void *scratchbuf;
> >   	int ret;
> >   
> > +	scratchbuf = kmemdup(val, len, GFP_KERNEL);
> > +	if (!scratchbuf)
> > +		return -ENOMEM;
> > +
> > +	op.data.buf.in = scratchbuf;
> >   	ret = spi_mem_exec_op(flash->spimem, &op);
> >   	if (ret < 0)
> >   		dev_err(&flash->spimem->spi->dev, "error %d reading %x\n", ret,
> >   			code);
> >   
> > +	kfree(scratchbuf);
> > +  
> 
> Actually this makes things even worse: "unrecognized JEDEC id bytes: b1, 
> 74, 01" since we don't copy scratchbuf to original buffer and kmemdup 
> before bus read is needless :-)

True :-).

I'll fix that and send a v2.

      reply	other threads:[~2018-09-17 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 13:36 [PATCH] mtd: devices: m25p80: Make the buffer passed in op is DMA-able Boris Brezillon
2018-09-17 13:38 ` Boris Brezillon
2018-09-17 14:13 ` Jarkko Nikula
2018-09-17 14:22   ` Boris Brezillon [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=20180917162237.49e6889f@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=richard@nod.at \
    --cc=stable@vger.kernel.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 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.