linux-kernel - Re: new module to check constant memory for corruption

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]

Date:	Mon, 14 Apr 2014 16:14:29 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Richard Weinberger <richard@....at>, Alexander.Kleinsorge@....de
cc:	andi@...stfloor.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: new module to check constant memory for corruption

On Sun, 13 Apr 2014, Richard Weinberger wrote:

> > Hi Richard,
> > 
> > I updated my code and check for ftrace (cat /proc/sys/kernel/ftrace_enabled > 0).
> > http://tauruz.homeip.net/ramcheck.tgz
> > 
> > On a 24/7 server ftrace is not a common thing anyway.
> 
> I disagree with you.
> perf, systemtap and other tools are widely used on "24/7" servers.

Plus the self-modifying code is present in other parts of kernel that have 
nothing to do with tracing as well. Consider static keys for example; they 
are used heavily in networking stack, scheduler code, etc.

-- 
Jiri Kosina
SUSE Labs

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