| 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: <n2m72cf309c1003310300k26b9aacbob7b49ff2f43f949d@mail.gmail.com>
Date: Wed, 31 Mar 2010 15:30:11 +0530
From: Sachin Pandhare <sachinpandhare@...il.com>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc: Sachin <sachinpandhare@...il.com>
Subject: kmemleak_scan_area
Hi Catalin,
In kmemleak.c file "kmemleak_scan_area" is appearing as a structure as
well as a function.
e.g.:
- struct kmemleak_scan_area_node {
- void __ref kmemleak_scan_area(const void *ptr, size_t size, gfp_t gfp)
Do you think it is a good to have it like that?
regards,
Sachin
--
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