All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Vincent Palatin" <vpalatin@chromium.org>,
	rtc-linux@googlegroups.com,
	"Alessandro Zummo" <a.zummo@towertech.it>,
	linux-kernel@vger.kernel.org,
	"Lothar Waßmann" <LW@KARO-electronics.de>
Subject: Re: [rtc-linux] [PATCH] rtc: recycle id when unloading a rtc driver
Date: Wed, 19 Dec 2012 09:55:02 +0100	[thread overview]
Message-ID: <50D180E6.3010305@ahsoftware.de> (raw)
In-Reply-To: <20121219002722.87438a08.akpm@linux-foundation.org>

Am 19.12.2012 09:27, schrieb Andrew Morton:
> On Wed, 19 Dec 2012 08:55:57 +0100 Alexander Holler <holler@ahsoftware.de> wrote:
>
>>>
>>> I'm all confused.
>>>
>>> Lothar's patch simply reverts Vincent's patch.  And that appears to be
>>> the correct thing to so, as the ida_simple_remove() in
>>> rtc_device_release() should be sufficient.
>>>
>>> But apparently that doesn't work, because Vincent was seeing the RTC
>>> ID's increment rather than getting reused.
>>>
>>> Is it the case that rtc_device_release() is not being called sometimes?
>>> If so, under what circumstances?
>>
>> Maybe something (sysfs or whatever) still has a reference to it. Vincent
>> should check that.
>>
>> But I'm sure the ID will be recycled with that put_device() in
>> unregister because I've got the same warning as Lothar did when
>> (porperly) removing an RTC (with kernel 3.7).
>
> If, as appears to be the case, rtc_device_release() is not being called
> then we're also leaking memory.  So yes please, it would be good if
> someone who can reproduce the IDs-dont-decrease problem could dive in
> and work out why ->release() isn't begin called.

Unlikely, as I've worked hard to get one of the first drivers for 
pluggable RTCs into the kernel. ;)
I think every sane kernel has them statically linked in and it's likely 
a problem of the RTC-driver Vincent experienced that with.

Regards,

Alexander

  reply	other threads:[~2012-12-19  8:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 23:53 [PATCH] rtc: recycle id when unloading a rtc driver Vincent Palatin
2012-12-19  0:46 ` [rtc-linux] " Andrew Morton
2012-12-19  7:37   ` Alexander Holler
2012-12-19  7:45     ` Andrew Morton
2012-12-19  7:55       ` Alexander Holler
2012-12-19  8:27         ` Andrew Morton
2012-12-19  8:55           ` Alexander Holler [this message]
2012-12-19 22:37             ` Andrew Morton
2012-12-19 22:58               ` Alexander Holler
2012-12-27 12:42             ` Alexander Holler

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=50D180E6.3010305@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=LW@KARO-electronics.de \
    --cc=a.zummo@towertech.it \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=vpalatin@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.