[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-block] [PATCH v2 1/2] trace: Remove trailing newline in events
From: |
John Snow |
Subject: |
Re: [Qemu-block] [PATCH v2 1/2] trace: Remove trailing newline in events |
Date: |
Mon, 16 Sep 2019 12:41:44 -0400 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 |
On 9/16/19 12:40 PM, Philippe Mathieu-Daudé wrote:
> On 9/16/19 6:36 PM, Eric Blake wrote:
>> On 9/16/19 4:51 AM, Philippe Mathieu-Daudé wrote:
>>> While the tracing frawework does not forbid trailing newline in
>>
>> framework
>>
>>> events format string, using them lead to confuse output.
>>> It is the responsibility of the backend to properly end an event
>>> line.
>>
>> Why just trailing newline? Should we not forbid ALL use of newline in a
>> trace message?
>
> I thought about it and forgot to add a comment when respining.
> Yes, I think this is the right thing to enforce.
> However it requires more cleanup, affecting more subsystems, so I'd
> rather keep it for a follow-up series.
What's the problem with using multi-line trace statements?
Does it interfere with non-printf backends?
(I think I intentionally use these for AHCI in a few places.)
--js
[Qemu-block] [PATCH v2 2/2] trace: Forbid event format ending with newline character, Philippe Mathieu-Daudé, 2019/09/16
Re: [Qemu-block] [PATCH v2 0/2] trace: Forbid trailing newline in event format, Stefan Hajnoczi, 2019/09/18