linux-kernel - [PATCH 0/1] function tracing: fix wrong position computing of stack

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

Message-Id: <1227236418-6023-1-git-send-email-liming.wang@windriver.com>
Date:	Fri, 21 Nov 2008 11:00:17 +0800
From:	Liming Wang <liming.wang@...driver.com>
To:	Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH 0/1] function tracing: fix wrong position computing of stack_trace

Hi Steven and Ingo,

Before I have submitted a patch to fix output of available_filter_functions,
later I checked other places that use seq_operations, I found stack_trace
also has this potential problem.

This fix use a more sane method to implement seq_operations. And this avoids
checking return value of seq_printf. If you think this implementation is OK,
I think others can be convert to this cleaner way, which will make future 
usage of seq_operations less errors.

walimis

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