public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-i2c@vger.kernel.org,
	"Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: do not use device name after device_unregister
Date: Wed, 13 Jan 2010 13:45:45 -0200	[thread overview]
Message-ID: <20100113154544.GA1400@holoscopio.com> (raw)
In-Reply-To: <20100113112515.3c73ceee@hyperion.delvare>

[-- Attachment #1: Type: text/plain, Size: 2821 bytes --]

On Wed, Jan 13, 2010 at 11:25:15AM +0100, Jean Delvare wrote:
> Hi Thadeu,
> 
> On Tue, 12 Jan 2010 19:36:43 -0200, Thadeu Lima de Souza Cascardo wrote:
> > dev_dbg outputs dev_name, which is released with device_unregister. This bug
> > resulted in output like this:
> > 
> > [ 7860.470713] i2c Xy2�0: adapter [SMBus I801 adapter at 1880] unregistered
> > 
> > The right output would be:
> > [   60.639233] i2c i2c-0: adapter [SMBus I801 adapter at 1880] unregistered
> 
> I can't reproduce this bug. Do you have a specific memory poisoning
> option enabled by any chance? And which kernel version are you running
> exactly?
> 

I'm not using any memory poisoning option that I'm aware of. However, I've been
using SLOB as an allocator, which may make a pretty difference, I guess.

I was running some of Linus' latest published git versions, something on top of
v2.6.33-rc3, commit 2c1f1895ef2aa8f0e5497893eff71304aef332e1.

> > 
> > Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
> > ---
> >  drivers/i2c/i2c-core.c |    5 +++--
> >  1 files changed, 3 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
> > index 0ac2f90..d5db0f4 100644
> > --- a/drivers/i2c/i2c-core.c
> > +++ b/drivers/i2c/i2c-core.c
> > @@ -843,6 +843,9 @@ int i2c_del_adapter(struct i2c_adapter *adap)
> >  				 adap->dev.parent);
> >  #endif
> >  
> > +	/* device name is gone after device_unregister */
> > +	dev_dbg(&adap->dev, "adapter [%s] unregistered\n", adap->name);
> > +
> >  	/* clean up the sysfs representation */
> >  	init_completion(&adap->dev_released);
> >  	device_unregister(&adap->dev);
> > @@ -855,8 +858,6 @@ int i2c_del_adapter(struct i2c_adapter *adap)
> >  	idr_remove(&i2c_adapter_idr, adap->nr);
> >  	mutex_unlock(&core_lock);
> >  
> > -	dev_dbg(&adap->dev, "adapter [%s] unregistered\n", adap->name);
> > -
> >  	/* Clear the device structure in case this adapter is ever going to be
> >  	   added again */
> >  	memset(&adap->dev, 0, sizeof(adap->dev));
> 
> The device structure is embedded in struct i2c_adapter, so its memory
> can't be reused before the i2c_adapter itself is freed, which can't
> happen before the end of function i2c_del_adapter(). Until recently,
> the device name was embedded in the device structure so the code above
> was fine. But apparently this changed some 9 months ago...
> 

The device may not be reused, but it's name is in its kobject, which allocates
memory using kvasprintf, and releases it when device_del ends up calling
kobject_put. So, anyway, we should not access memory that has been released. I
guess trying some poisoning option or changing to SLOB may help you hit the
bug.

> -- 
> Jean Delvare

Best Regards,
Cascardo.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2010-01-13 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 21:36 [PATCH] i2c: do not use device name after device_unregister Thadeu Lima de Souza Cascardo
2010-01-13 10:25 ` Jean Delvare
2010-01-13 10:38   ` Manu Abraham
2010-01-13 15:45   ` Thadeu Lima de Souza Cascardo [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=20100113154544.GA1400@holoscopio.com \
    --to=cascardo@holoscopio.com \
    --cc=ben-linux@fluff.org \
    --cc=khali@linux-fr.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox