Pali Rohár wrote: > Have I missed something? setsockopt() solution which I described in > <20200419234937.4zozkqgpt557m3o6@pali> email is already runtime option. I think what Luiz meant was that there has to be a module option that enables the additional kernel code, for example modprobe bluetooth enable_voice_setup=1 This would enable us interested folk to test the changes, while they cannot blow up other peoples Bluetooth stack. At least that's the reasoning that I assume. The setsockopt() is a runtime option on the application side but doesn't "protect" the kernel. Content-wise, I understand Luiz' message as an approval of the general API you proposed, as long as it is not active by default. Best regards, Jan-Philipp
