linux-kernel - Re: [PATCH 2.6.28-rc5 04/11] kmemleak: Add modules support

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 20 Nov 2008 13:03:14 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.28-rc5 04/11] kmemleak: Add modules support


small nit:

> +#else
> +static inline void memleak_load_module(struct module *mod, Elf_Ehdr *hdr,
> +				       Elf_Shdr *sechdrs, char *secstrings)
> +{ }
> +#endif

this looks nicer:

static inline void
memleak_load_module(struct module *mod, Elf_Ehdr *hdr, Elf_Shdr *sechdrs,
		    char *secstrings)
{
}

We dont use "{ }" in other places in the kernel, so lets not invent a 
new style if possible.

> +	/* the pointer to this block is stored in the module structure
> +	 * which is inside the block. Just mark it as not being a
> +	 * leak */

Comment style.

> +	/* the pointer to this block is stored in the module structure
> +	 * which is inside the block. This block doesn't need to be
> +	 * scanned as it contains data and code that will be freed
> +	 * after the module is initialized */

ditto.

Thanks,

	Ingo
--
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/