> On 27-Feb-2024, at 10:38 PM, Steven Rostedt <rost...@goodmis.org> wrote:
>
> On Tue, 27 Feb 2024 11:56:14 -0500
> Steven Rostedt <rost...@goodmis.org> wrote:
>
>> On Tue, 27 Feb 2024 22:08:18 +0530
>> Sachin Sant <sach...@linux.ibm.com> wrote:
>>
>>>> Can you apply this, and see if it triggers and if it does, print the line
>>>> that has the max size?
>>>>
>>>
>>> With this I see following trace
>>>
>>> [ 61.327138] ------------[ cut here ]------------
>>> [ 61.327159] MAX OUT OF RANGE 63492
>>
>> Well I guess there you have it ;-)
>>
>> vsprintf() doesn't like a precision of 63492!
>>
>> I'll look to see what the best way to deal with this is.
>
> Does this fix it?
>
Thank You. Yup this fixes the reported problem.
# ./ftracetest test.d/00basic/trace_marker.tc
=== Ftrace unit tests ===
[1] Basic tests on writing to trace_marker [PASS]
[2] (instance) Basic tests on writing to trace_marker [PASS]
# of passed: 2
# of failed: 0
# of unresolved: 0
# of untested: 0
# of unsupported: 0
# of xfailed: 0
# of undefined(test bug): 0
#
Remaining test also completed without any issues. Based on the test results
Tested-by: Sachin Sant <sach...@linux.ibm.com>
Thanks
— Sachin
