From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: Philip Guo <pg@cs.stanford.edu>, Jeff Garzik <jeff@garzik.org>,
ahennessy@mvista.com, netdev@vger.kernel.org
Subject: Re: possible bug in net/tc35815.c in linux-2.6.19
Date: Sat, 24 Feb 2007 13:37:55 +0100 [thread overview]
Message-ID: <45E031A3.806@googlemail.com> (raw)
In-Reply-To: <45DFEC09.3020801@cs.stanford.edu>
Hi Philip,
Philip Guo napisał(a):
> Hi,
>
> I am a graduate student working on finding bugs in Linux drivers using
> an automated research tool. I think I've found a possible bug in
> net/tc35815.c, and I'd appreciate it if you could confirm/disconfirm it.
>
> Thanks,
> Philip
>
> ---
> net/tc35815.c
>
> tc35815_driver is never unregistered in tc35815_cleanup_module()
>
> static int __init tc35815_init_module(void)
> {
> return pci_register_driver(&tc35815_driver);
> }
>
> static void __exit tc35815_cleanup_module(void)
> {
> struct net_device *next_dev;
>
> while (root_tc35815_dev) {
> struct net_device *dev = root_tc35815_dev;
> next_dev = ((struct tc35815_local *)dev->priv)->next_module;
> iounmap((void *)(dev->base_addr));
> unregister_netdev(dev);
> free_netdev(dev);
> root_tc35815_dev = next_dev;
> }
> }
>
>
I think that you are right, but I don't know this code.
Jeff, what do you think about this?
Regards,
Michal
PS. Philip, please sign this patch.
--
Michal K. K. Piotrowski
LTG - Linux Testers Group (PL)
(http://www.stardust.webpages.pl/ltg/)
LTG - Linux Testers Group (EN)
(http://www.stardust.webpages.pl/linux_testers_group_en/)
Signed-off-by: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
--- linux-mm-clean/drivers/net/tc35815.c 2007-02-04 19:44:54.000000000 +0100
+++ linux-mm/drivers/net/tc35815.c 2007-02-24 13:07:34.000000000 +0100
@@ -1740,6 +1740,8 @@ static void __exit tc35815_cleanup_modul
free_netdev(dev);
root_tc35815_dev = next_dev;
}
+
+ pci_unregister_driver(&tc35815_driver);
}
module_init(tc35815_init_module);
module_exit(tc35815_cleanup_module);
next parent reply other threads:[~2007-02-24 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45DFEC09.3020801@cs.stanford.edu>
2007-02-24 12:37 ` Michal Piotrowski [this message]
2007-02-24 22:04 ` possible bug in net/tc35815.c in linux-2.6.19 Jeff Garzik
2007-02-26 10:26 ` Ralf Baechle
2007-02-26 11:05 ` Atsushi Nemoto
2007-02-26 20:07 ` Sergei Shtylyov
2007-02-27 14:55 ` Atsushi Nemoto
2007-02-27 14:58 ` rbhma4500_defconfig Atsushi Nemoto
2007-02-27 15:21 ` rbhma4500_defconfig Sergei Shtylyov
2007-02-28 14:07 ` rbhma4500_defconfig Atsushi Nemoto
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=45E031A3.806@googlemail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=ahennessy@mvista.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=pg@cs.stanford.edu \
/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.