linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: David Brownell <dbrownell@users.sourceforge.net>,
	Eric Miao <eric.y.miao@gmail.com>,
	Vasily Khoruzhick <anarsoul@gmail.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	spi-devel-general@lists.sourceforge.net,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] pxa2xx_spi: fix memory corruption
Date: Mon, 18 Jul 2011 11:10:30 +0100	[thread overview]
Message-ID: <20110718101030.GS23270@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110715213106.GM2833@ponder.secretlab.ca>

On Fri, Jul 15, 2011 at 03:31:06PM -0600, Grant Likely wrote:
> ... plus care must be taken not to accidentally reload the line into
> cache after it has been pushed out for DMA, which is a risk on
> structures with embedded DMA buffers if other non-DMA elements end up
> in the same cache line.  This is the situation I was wondering about.

I don't think it matters one bit in this case - we're not caring about
the actual data read/written in the DMA, we just need to do DMA to
keep the controller happy.  That's especially true as we don't set the
address increment bit in the DMA command register, so we end up accessing
the same RAM location time and time again for each DMA transfer.

So please, merge the patch - it fixes a serious memory-scribbling bug.

  reply	other threads:[~2011-07-18 10:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09 21:14 [PATCH] pxa2xx_spi: fix memory corruption Vasily Khoruzhick
2011-07-09 23:05 ` Marek Vasut
2011-07-09 23:11   ` Russell King - ARM Linux
2011-07-10  7:14     ` Marek Vasut
     [not found]       ` <201107100914.45452.marek.vasut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-07-10  7:57         ` Marek Vasut
2011-07-10 12:09           ` [PATCH v2] " Vasily Khoruzhick
2011-07-10 12:43             ` Marek Vasut
2011-07-10 13:09               ` Vasily Khoruzhick
2011-07-10 15:18                 ` [PATCH v3] " Vasily Khoruzhick
     [not found]                   ` <1310311099-24638-1-git-send-email-anarsoul-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-07-14 12:17                     ` Vasily Khoruzhick
     [not found]                       ` <201107141517.36147.anarsoul-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-07-14 12:21                         ` Marek Vasut
2011-07-15  2:53                     ` Grant Likely
2011-07-15  8:12                       ` Russell King - ARM Linux
     [not found]                         ` <20110715081242.GM23270-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2011-07-15 19:50                           ` Grant Likely
2011-07-15 20:24                             ` Russell King - ARM Linux
2011-07-15 21:31                               ` Grant Likely
2011-07-18 10:10                                 ` Russell King - ARM Linux [this message]
2011-07-18  7:56                       ` Vasily Khoruzhick
     [not found]                         ` <201107181056.51782.anarsoul-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-11-29 14:05                           ` Vasily Khoruzhick
2011-11-29 14:31                             ` Marek Vasut
2011-12-07 20:35                             ` Wolfram Sang
     [not found]                               ` <20111207203559.GB3744-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-12-08  8:19                                 ` [RESEND PATCH " Vasily Khoruzhick

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=20110718101030.GS23270@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=anarsoul@gmail.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=eric.y.miao@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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).