I've activated logs for wireguard, effectively I want to disable them now - first, the journey takes me to understanding what was added, therefore this question here.

I activated the logs with this cmd:
# modprobe wireguard && echo module wireguard +p > /sys/kernel/debug/dynamic_debug/control

I want to understand what was added to the file. When running echo module wireguard +p I don't get any results, echos manpage doesn't list information about this +p thingy.

could you please enlighten me, what +p does?

  • This is something that the first hit in a google search for your command is likely to answer. Furthermore, it's not about managing business IT.
    – vidarlo
    Feb 25, 2023 at 13:45

2 Answers 2


In this case, the +p is a kernel debug directive where + adds the given flag to the configuration and the given flag p in this case will enable the pr_debug() callsite. The echo command simply writes to the dynamic debug configuration file at /sys/kernel/debug/dynamic_debug/control. For a more detailed explanation Dynamic Debug - The Linux Kernel documentation.

  • 1
    So basically -p disables dynamic debugging.
    – W.M.
    Jun 18, 2023 at 18:19
  • 1
    @W.M. Yes, that is correct.
    – psiryn
    Sep 4, 2023 at 19:44

I know one user already gave the link to the kernel doc, but for the lazy one, there are others flags beside the p.

The flags are (from kernel docs):

p    enables the pr_debug() callsite.
f    Include the function name in the printed message
l    Include line number in the printed message
m    Include module name in the printed message
t    Include thread ID in messages not generated from interrupt context

So to enable them from the question above do echo module wireguard +pfm > /sys/kernel/debug/dynamic_debug/control.

To remove them just do echo module wireguard -pfm > /sys/kernel/debug/dynamic_debug/control.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .