From: zajec5@gmail.com (Rafał Miłecki)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH V3] axi: add AXI bus driver
Date: Mon, 11 Apr 2011 23:36:39 +0200 [thread overview]
Message-ID: <BANLkTingqXAWTeOhcL6ER0UJfEdQF5Bo2A@mail.gmail.com> (raw)
In-Reply-To: <20110411212513.GA17809@kroah.com>
2011/4/11 Greg KH <greg@kroah.com>:
> On Mon, Apr 11, 2011 at 11:19:13PM +0200, Rafa? Mi?ecki wrote:
>> 2011/4/11 Greg KH <greg@kroah.com>:
>> > On Mon, Apr 11, 2011 at 11:25:14PM +0200, Rafa? Mi?ecki wrote:
>> >> +static void axi_release_core_dev(struct device *dev)
>> >> +{
>> >> + ? ? /* Silent lack-of-release warning */
>> >> +}
>> >
>> > Ok, WTF!!!!
>>
>> Thank you for your kindly words. It's much more enjoyable to work on
>> kernel that way. I definitely made that on purpose.
>
> I can't tell if you are kidding or not.
That was 100% irony. I swear I don't enjoy publishing bad code and
getting such a comment.
> Please read the documentation for how to do this properly. ?I find it
> really hard to believe that you wrote that comment instead of putting in
> the 2 lines of code required for this function.
>
> Especially as-it-is, your code does not work properly and leaks memory
> badly. ?Why would you do that on purpose?
I tried to read some documentation about this.
1) driver-mode/device.txt says only that:
> Callback to free the device after all references have
> gone away. This should be set by the allocator of the
> device (i.e. the bus driver that discovered the device).
I *really* do not know how my driver should "free" core on AXI bus.
2) LDD3 says:
> The method is called when the last reference to the device is removed; it is called
> from the embedded kobject?s release method. All device structures registered with
> the core must have a release method, or the kernel prints out scary complaints.
Well, I do not register any structs for AXI core.
3) Example code from LDD3:
static void ldd_bus_release(struct device *dev)
{
printk(KERN_DEBUG "lddbus release\n");
}
Yeah, that's what I did...
4) SSB in it's ssb_release_dev just calls kfree on struct that was
allocated when registering drivers. *I do not* allocate such a struct,
so I believe I do exactly the same memory leak as SSB does.
Can you spend 2 more minues in addition to commenting my ideas and
help me with writing that 2 lines I missed? Where do I leak memory in
my driver? Which struct should I kfree?
--
Rafa?
next prev parent reply other threads:[~2011-04-11 21:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 21:25 [RFC][PATCH V3] axi: add AXI bus driver Rafał Miłecki
2011-04-11 21:06 ` Greg KH
2011-04-11 21:19 ` Rafał Miłecki
2011-04-11 21:25 ` Greg KH
2011-04-11 21:36 ` Rafał Miłecki [this message]
2011-04-11 21:56 ` Greg KH
2011-04-11 22:12 ` Rafał Miłecki
2011-04-11 22:36 ` Greg KH
2011-04-11 22:45 ` Rafał Miłecki
2011-04-11 23:35 ` Greg KH
2011-04-12 5:41 ` Rafał Miłecki
2011-04-12 11:40 ` Rafał Miłecki
2011-04-12 15:16 ` Greg KH
2011-04-12 15:14 ` Greg KH
2011-04-12 15:25 ` Rafał Miłecki
2011-04-11 21:07 ` Greg KH
2011-04-11 23:44 ` Joe Perches
2011-04-12 5:52 ` Rafał Miłecki
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=BANLkTingqXAWTeOhcL6ER0UJfEdQF5Bo2A@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).