From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Rolf Eike Beer" <eike-kernel@sf-tec.de>
Cc: "Alessandro Zummo" <alessandro.zummo@towertech.it>,
"Andrew Morton" <akpm@osdl.org>,
linux-kernel@vger.kernel.org, "Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [RTC] Remove superfluous call to call to cdev_del()
Date: Thu, 21 Sep 2006 10:44:24 -0400 [thread overview]
Message-ID: <d120d5000609210744w4c52bcf0qda2c3b9f12d4c2d3@mail.gmail.com> (raw)
In-Reply-To: <200609211030.07944.eike-kernel@sf-tec.de>
On 9/21/06, Rolf Eike Beer <eike-kernel@sf-tec.de> wrote:
> Alessandro Zummo wrote:
> > On Thu, 21 Sep 2006 09:46:06 +0200
> >
> > Rolf Eike Beer <eike-kernel@sf-tec.de> wrote:
> > > If cdev_add() fails there is no good reason to call cdev_del().
> > >
> > > Signed-off-by: Rolf Eike Beer <eike-kernel@sf-tec.de>
> > >
> > > rtc->char_dev.owner = rtc->owner;
> > >
> > > if (cdev_add(&rtc->char_dev, MKDEV(MAJOR(rtc_devt), rtc->id), 1)) {
> > > - cdev_del(&rtc->char_dev);
> > > dev_err(class_dev->dev,
> > > "failed to add char device %d:%d\n",
> > > MAJOR(rtc_devt), rtc->id);
> >
> > I'm not sure.. this is drivers/char/raw.c:
> >
> >
> > cdev_init(&raw_cdev, &raw_fops);
> > if (cdev_add(&raw_cdev, dev, MAX_RAW_MINORS)) {
> > kobject_put(&raw_cdev.kobj);
> > unregister_chrdev_region(dev, MAX_RAW_MINORS);
> > goto error;
> > }
> >
> > in case of failure, it does a kobject_put.
> > tha same call is done by cdev_del.
But cdev_del also tries to do kobj_unmap before doing kobject_put. If
cdev_add fails the object is not added to the map so we shoult not try
to unmap it (although it does not hurt in the current implementation).
>
> This is unneeded here as it's embedded into struct rtc_device. Jonathan?
>
cdev distingueshes between stattically and synamically allocated
objects and so it is safe to do kobject_put/cdev_del even on cdevs
embedded into other structures.
> > other drivers have implemented different error paths.
> > which one is correct?
>
raw.c seems to be DTRT.
> Probably half of them are wrong, ugly or both. I think this interface is not
> very intuitive at all. This two calls needed to set up an embedded cdev are
> IMHO the best way to keep people confused. At least the (possible) need to
> call cdev_del() on failed cdev_add() is just weird.
>
The rule is simple - after cdev_init/cdev_alloc call kobject_put.
After successful cdev_add call cdev_del.
--
Dmitry
prev parent reply other threads:[~2006-09-21 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 7:46 Rolf Eike Beer
2006-09-21 7:56 ` Alessandro Zummo
2006-09-21 8:30 ` Rolf Eike Beer
2006-09-21 14:44 ` Dmitry Torokhov [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=d120d5000609210744w4c52bcf0qda2c3b9f12d4c2d3@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@osdl.org \
--cc=alessandro.zummo@towertech.it \
--cc=corbet@lwn.net \
--cc=eike-kernel@sf-tec.de \
--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
all inboxes | Powered by JetHome®