mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, Tony Jones <tonyj@suse.de>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	Stephen Street <stephen@streetfiresound.com>
Subject: Re: [PATCH] spi: Fix double-free on spi_unregister_master
Date: Thu, 8 Nov 2007 10:42:13 -0800	[thread overview]
Message-ID: <200711081042.14200.david-b@pacbell.net> (raw)
In-Reply-To: <20071108.233505.25913499.anemo@mba.ocn.ne.jp>

On Thursday 08 November 2007, Atsushi Nemoto wrote:
> After 49dce689ad4ef0fd1f970ef762168e4bd46f69a3, device_for_each_child
> iteration hits the master device itself.  Do not call
> spi_unregister_device() for the master device.
> 
> Signed-off-by: Atsushi Nemoto <anemo@mba.ocn.ne.jp>

ACK, and thanks.  Regression against 2.6.23...

I should have searched for other device_for_each_child() calls
when I had to do the same thing to fix the mmc_spi breakage.

Looks like the pxa2xx_spi suspend() code probably broke too.
I CC'd the maintainer of that code, though I'm not sure how
much time he has for this lately.

I'll hope someone else checks for non-SPI driver stacks which
such "class_dev" elimination may have broke...


> ---
>  drivers/spi/spi.c |    8 +++++---
>  1 files changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index 89769ce..b31f443 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -457,10 +457,11 @@ done:
>  EXPORT_SYMBOL_GPL(spi_register_master);
>  
>  
> -static int __unregister(struct device *dev, void *unused)
> +static int __unregister(struct device *dev, void *master_dev)
>  {
>  	/* note: before about 2.6.14-rc1 this would corrupt memory: */
> -	spi_unregister_device(to_spi_device(dev));
> +	if (dev != master_dev)
> +		spi_unregister_device(to_spi_device(dev));
>  	return 0;
>  }
>  
> @@ -478,7 +479,8 @@ void spi_unregister_master(struct spi_master *master)
>  {
>  	int dummy;
>  
> -	dummy = device_for_each_child(master->dev.parent, NULL, __unregister);
> +	dummy = device_for_each_child(master->dev.parent, &master->dev,
> +					__unregister);
>  	device_unregister(&master->dev);
>  }
>  EXPORT_SYMBOL_GPL(spi_unregister_master);
> 



      reply	other threads:[~2007-11-08 19:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 14:35 Atsushi Nemoto
2007-11-08 18:42 ` David Brownell [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=200711081042.14200.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@linux-foundation.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stephen@streetfiresound.com \
    --cc=tonyj@suse.de \
    /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

all inboxes | Powered by JetHome®