From: Andrew Morton <akpm@linux-foundation.org>
To: Vincent Palatin <vpalatin@chromium.org>
Cc: rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org
Subject: Re: [rtc-linux] [PATCH] rtc: recycle id when unloading a rtc driver
Date: Tue, 18 Dec 2012 16:46:59 -0800 [thread overview]
Message-ID: <20121218164659.a3d3655a.akpm@linux-foundation.org> (raw)
In-Reply-To: <1343951605-25722-1-git-send-email-vpalatin@chromium.org>
On Thu, 2 Aug 2012 16:53:25 -0700
Vincent Palatin <vpalatin@chromium.org> wrote:
> When calling rtc_device_unregister, we are not freeing the id used by the
> driver.
> So when doing a unload/load cycle for a RTC driver (e.g. rmmod rtc_cmos
> && modprobe rtc_cmos), its id is incremented by one. As a consequence,
> we no longer have neither an rtc0 driver nor a /proc/driver/rtc (as it
> only exists for the first driver).
>
> Signed-off-by: Vincent Palatin <vpalatin@chromium.org>
> ---
> drivers/rtc/class.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/rtc/class.c b/drivers/rtc/class.c
> index dc4c274..37b1d82 100644
> --- a/drivers/rtc/class.c
> +++ b/drivers/rtc/class.c
> @@ -238,6 +238,7 @@ void rtc_device_unregister(struct rtc_device *rtc)
> rtc_proc_del_device(rtc);
> device_unregister(&rtc->dev);
> rtc->ops = NULL;
> + ida_simple_remove(&rtc_ida, rtc->id);
> mutex_unlock(&rtc->ops_lock);
> put_device(&rtc->dev);
> }
Now I think about it, this shouldn't have been needed?
That put_device() should call rtc_device_release(), which does the
ida_simple_remove(). Isn't that working?
next prev parent reply other threads:[~2012-12-19 0:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 23:53 Vincent Palatin
2012-12-19 0:46 ` Andrew Morton [this message]
2012-12-19 7:37 ` [rtc-linux] " 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
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=20121218164659.a3d3655a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome