On 11/30/2018 05:57 PM, Pavel Butsykin wrote:
> Hmm, __kfuse_trace() duplicates message to debugfs trace, without '\n'
Yes, and AFAIS most of the existing messages already come w/o it.
> this messages will look weird. We need to fix __kfuse_trace() by adding
> concatenation '\n' (or even drop
Would you like to fix all FUSE_KTRACE's in the kernel? I see a few more
FUSE_KTRACE with '\n'.
On 30.11.2018 17:23, Pavel Emelianov wrote:
> After a recent (b)log (re)work it was noticed that some extra \n-s crept
> into the classical log files. Indeed, the pstorage TRACE() call appends a
> \n at
After a recent (b)log (re)work it was noticed that some extra \n-s crept
into the classical log files. Indeed, the pstorage TRACE() call appends a
\n at the end of each message and so does the kernel code.
Sorry for inconvenience.
https://pmc.acronis.com/browse/VSTOR-18383
Signed-off-by:
