| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1436368397-30502-1-git-send-email-jthumshirn@suse.de>
Date: Wed, 8 Jul 2015 17:13:17 +0200
From: Johannes Thumshirn <jthumshirn@...e.de>
To: linux-kernel@...r.kernel.org
Cc: Johannes Thumshirn <jthumshirn@...e.de>
Subject: [PATCH] c2port: Destroy c2port_idr on module exit
Destroy c2port_idr on module exit, reclaiming the allocated memory.
This was detected by the following semantic patch (written by Luis Rodriguez
<mcgrof@...e.com>)
<SmPL>
@ defines_module_init @
declarer name module_init, module_exit;
declarer name DEFINE_IDR;
identifier init;
@@
module_init(init);
@ defines_module_exit @
identifier exit;
@@
module_exit(exit);
@ declares_idr depends on defines_module_init && defines_module_exit @
identifier idr;
@@
DEFINE_IDR(idr);
@ on_exit_calls_destroy depends on declares_idr && defines_module_exit @
identifier declares_idr.idr, defines_module_exit.exit;
@@
exit(void)
{
...
idr_destroy(&idr);
...
}
@ missing_module_idr_destroy depends on declares_idr && defines_module_exit && !on_exit_calls_destroy @
identifier declares_idr.idr, defines_module_exit.exit;
@@
exit(void)
{
...
+idr_destroy(&idr);
}
</SmPL>
Signed-off-by: Johannes Thumshirn <jthumshirn@...e.de>
---
drivers/misc/c2port/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/misc/c2port/core.c b/drivers/misc/c2port/core.c
index 464419b..16f0116 100644
--- a/drivers/misc/c2port/core.c
+++ b/drivers/misc/c2port/core.c
@@ -999,6 +999,7 @@ static int __init c2port_init(void)
static void __exit c2port_exit(void)
{
class_destroy(c2port_class);
+ idr_destroy(&c2port_idr);
}
module_init(c2port_init);
--
2.4.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists