linux-kernel - Re: Kmemleak for mips

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] [day] [month] [year] [list]

Message-Id: <1257240227.22183.3.camel@pc1117.cambridge.arm.com>
Date:	Tue, 03 Nov 2009 09:23:47 +0000
From:	Catalin Marinas <catalin.marinas@....com>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	subscriptions@...oomer.com, linux-mm@...ck.org,
	Pekka Enberg <penberg@...helsinki.fi>,
	"John W. Linville" <linville@...driver.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Kmemleak for mips

On Mon, 2009-11-02 at 09:07 -0800, Luis R. Rodriguez wrote:
> Curious what the limitations are on restricting kmemleak to non-mips
> archs. I have a user and situation [1] where this could be helpful [1]
> in debugging an issue. The user reports he cannot enable it on mips.

It may just work but cannot be enabled because I cannot test kmemleak on
such hardware. In general you need to make sure that the _sdata/_edata
and __bss_start/__bss_stop symbols are defined. If there are other ways
of allocating memory than the standard API, it would need additional
hooks. Some false-positives specific to MIPS may need to be annotated
(usually with kmemleak_not_leak).

(btw, you could also merge the kmemleak.git tree on git.kernel.org as it
has improvements on the rate of false positives; the patches will be
pushed in 2.6.33-rc1)

-- 
Catalin

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