Right now we enable cifsFYI logs unconditionally when capturing diagnostics. But this makes changes to debugfs, which will not be possible with kernel lockdown enabled, and that is the default with trusted VMs which are becoming more common.
Additionally, we do not use verbose logs much for our debugging. We have grown to use trace-cmd more.
This change disables verbose logging by default.
No need to document this. It will complicate the instructions for the customers. Instruct customers specially when verbose logs are needed.
Right now we enable cifsFYI logs unconditionally when capturing diagnostics. But this makes changes to debugfs, which will not be possible with kernel lockdown enabled, and that is the default with trusted VMs which are becoming more common.
Additionally, we do not use verbose logs much for our debugging. We have grown to use trace-cmd more.
This change disables verbose logging by default.
No need to document this. It will complicate the instructions for the customers. Instruct customers specially when verbose logs are needed.