On 2024/06/27 8:52, Alexei Starovoitov wrote: >>> Sorry, but it makes no sense to put the burden of the >>> printk_deferred_enter() on the BPF hook logic. It should sit solely >>> with the code that actually calls printk(). >> >> How do you respond to Petr Mladek's comment >> >> Yeah, converting printk() into printk_deferred() or using >> printk_deferred_enter() around particular code paths is a whac-a-mole >> game. > > Exactly. wrapping bpf with printk_deferred_enter() is such a whac-a-mole. > It doesn't fix an issue. Then, what change do you propose?
