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  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:	Mon, 07 Apr 2014 14:29:46 +0900
From:	Namhyung Kim <>
To:	Jiri Olsa <>
Cc:	Masami Hiramatsu <>,
	Namhyung Kim <>,
	LKML <>,
	Peter Zijlstra <>,
	Arnaldo Carvalho de Melo <>,
	Paul Mackerras <>,
	Ingo Molnar <>
Subject: Re: [PATCH -tip ] [BUGFIX] perf/probe: Fix to handle errors in line_range searching

On Sun, 6 Apr 2014 14:52:48 +0200, Jiri Olsa wrote:
> On Wed, Apr 02, 2014 at 02:48:31PM +0900, Masami Hiramatsu wrote:
>> As Namhyung reported(,
>> current perf-probe -L option doesn't handle errors in line-range
>> searching correctly. It causes a SEGV if an error occured in the
>> line-range searching.
>>   ----
>>   $ perf probe -x ./perf -v -L map__load
>>   Open Debuginfo file: /home/namhyung/project/linux/tools/perf/perf
>>   fname: util/map.c, lineno:153
>>   New line range: 153 to 2147483647
>>   path: (null)
>>   Segmentation fault (core dumped)
>>   ----
>> This is because line_range_inline_cb() ignores errors
>> from find_line_range_by_line() which means that lr->path is
>> already freed on the error path in find_line_range_by_line().
>> As a result, get_real_path() accesses the lr->path and it
>> causes a NULL pointer exception.
>> This fixes line_range_inline_cb() to handle the error correctly,
>> and report it to the caller.
>> Anyway, this just fixes a possible SEGV bug, Namhyung's patch
>> is also required.
> will take both.. Namhyung, ack to Masami's change?


Acked-by: Namhyung Kim <>

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists