public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: marek.vasut@gmail•com (Marek Vasut)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] pxa2xx_spi: fix memory corruption
Date: Sun, 10 Jul 2011 01:05:48 +0200	[thread overview]
Message-ID: <201107100105.48168.marek.vasut@gmail.com> (raw)
In-Reply-To: <1310246098-21208-1-git-send-email-anarsoul@gmail.com>

On Saturday, July 09, 2011 11:14:58 PM Vasily Khoruzhick wrote:
> pxa2xx_spi_probe allocates struct driver_data and null_dma_buf
> at same time via spi_alloc_master(), but then calculates
> null_dma_buf pointer incorrectly, and it causes memory corruption
> later if DMA usage is enabled.
> 
> Signed-off-by: Vasily Khoruzhick <anarsoul@gmail•com>
> ---
>  drivers/spi/pxa2xx_spi.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/spi/pxa2xx_spi.c b/drivers/spi/pxa2xx_spi.c
> index dc25bee..ef38fbf 100644
> --- a/drivers/spi/pxa2xx_spi.c
> +++ b/drivers/spi/pxa2xx_spi.c
> @@ -1569,7 +1569,7 @@ static int __devinit pxa2xx_spi_probe(struct
> platform_device *pdev) master->transfer = transfer;
> 
>  	drv_data->ssp_type = ssp->type;
> -	drv_data->null_dma_buf = (u32 *)ALIGN((u32)(drv_data +
> +	drv_data->null_dma_buf = (u32 *)ALIGN(((u32)drv_data +
>  						sizeof(struct driver_data)), 8);

This thing looks a bit disturbing in itself. Like, where the heck is that thing 
pointing in the end ? Since some data are written to address in "null_dma_buf" 
... isn't this just changing the corruption impact ?
> 
>  	drv_data->ioaddr = ssp->mmio_base;

  reply	other threads:[~2011-07-09 23:05 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 [this message]
2011-07-09 23:11   ` Russell King - ARM Linux
2011-07-10  7:14     ` Marek Vasut
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
2011-07-14 12:17                 ` Vasily Khoruzhick
2011-07-14 12:21                   ` Marek Vasut
2011-07-15  2:53                 ` Grant Likely
2011-07-15  8:12                   ` Russell King - ARM Linux
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
2011-07-18  7:56                   ` Vasily Khoruzhick
2011-11-29 14:05                     ` Vasily Khoruzhick
2011-11-29 14:31                       ` Marek Vasut
2011-12-07 20:35                       ` Wolfram Sang
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=201107100105.48168.marek.vasut@gmail.com \
    --to=marek.vasut@gmail$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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