linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Mark Brown
	<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
Subject: Re: [PATCH 1/3] spi/stmp: Fix device remove function
Date: Fri, 24 Aug 2012 10:12:20 -0700	[thread overview]
Message-ID: <20120824171220.GA4591@roeck-us.net> (raw)
In-Reply-To: <20120824084708.GB12630-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

On Fri, Aug 24, 2012 at 10:47:08AM +0200, Wolfram Sang wrote:
> On Thu, Aug 23, 2012 at 08:08:47PM -0700, Guenter Roeck wrote:
> > The call sequence spi_alloc_master/spi_register_master/spi_unregister_master
> > is complete; it reduces the device reference count to zero, which results in
> > device memory being freed. The remove function accesses the freed memory after
> > the call to spi_unregister_master(), _and_ it calls spi_master_put on the freed
> > memory.
> > 
> > Acquire a reference to the SPI master device and release it after cleanup is
> > complete (with the existing spi_master_put) to solve the problem.
> > 
> > Also, the device subsystem ensures that the remove function is only called once,
> > and resets device driver data to NULL. Remove the respective check and drop the
> > unnecessaary call to platform_set_drvdata().
> > 
> > Signed-off-by: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
> > ---
> > Note that this driver is impossible to build, since it depends on ARCH_STMP3XXX
> > which is not defined anywhere.
> 
> It can be replaced with the spi driver for mxs once it is mainline.
> 
Maybe the driver should be removed then.

The mxs driver has exactly the same problem as the one fixed with this patch.
I'll submit a patch for it.

Guenter

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

  parent reply	other threads:[~2012-08-24 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24  3:08 [PATCH 1/3] spi/stmp: Fix device remove function Guenter Roeck
     [not found] ` <20120824084708.GB12630@pengutronix.de>
     [not found]   ` <20120824084708.GB12630-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-08-24 17:12     ` Guenter Roeck [this message]
     [not found] ` <1345777729-19342-1-git-send-email-linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2012-08-24  3:08   ` [PATCH 2/3] spi/tegra: " Guenter Roeck
2012-08-24  3:08   ` [PATCH 3/3] spi/topcliff-pch: " Guenter Roeck
2012-08-27 16:38   ` [PATCH 1/3] spi/stmp: " Mark Brown

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=20120824171220.GA4591@roeck-us.net \
    --to=linux-0h96xk9xttrk1umjsbkqmq@public.gmane.org \
    --cc=broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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 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).