linux-kernel - Re: [PATCH] ftracetest: Cope properly with stack tracer not being enabled

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: <551AC894.40101@osg.samsung.com>
Date:	Tue, 31 Mar 2015 10:17:24 -0600
From:	Shuah Khan <shuahkh@....samsung.com>
To:	Steven Rostedt <rostedt@...dmis.org>,
	Michael Ellerman <mpe@...erman.id.au>
CC:	linux-kernel@...r.kernel.org, davej@...emonkey.org.uk,
	namhyung@...nel.org
Subject: Re: [PATCH] ftracetest: Cope properly with stack tracer not being
 enabled

On 03/30/2015 03:36 PM, Steven Rostedt wrote:
> On Mon, 30 Mar 2015 16:21:40 +1100
> Michael Ellerman <mpe@...erman.id.au> wrote:
> 
>> If the stack tracer (CONFIG_STACK_TRACER) is disabled, the
>> fgraph-filter-stack test blows chunks:
>>
>>   [8] ftrace - function graph filters with stack tracer	[FAIL]
>>   + reset_tracer
>>   + echo nop
>>   ./ftracetest: 19: /home/michael/selftests/ftrace/test.d/ftrace/fgraph-filter-stack.tc:
>>   	cannot create /proc/sys/kernel/stack_tracer_enabled: Directory nonexistent
>>
>> Fix it by checking if the proc file exists before echoing to it. With
>> the patch applied it fails correctly with:
>>
>>   [8] ftrace - function graph filters with stack tracer	[UNSUPPORTED]
>>
>> Signed-off-by: Michael Ellerman <mpe@...erman.id.au>
>> ---
> 
> Acked-by: Steven Rostedt <rostedt@...dmis.org>
> 

Applied to linux-kselftest next for 4.1

thanks,
-- Shuah


-- 
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@....samsung.com | (970) 217-8978
--
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/