On 23/02/2023 17:07, Larry Finger wrote:
There are various tasks/applications that generate this warning early after startup, but the ones from `Qt bearer threa' are the ones that persist. Those were the only ones that I had seen once the dmesg buffer wrapped around. Obviously any kind on "once" restriction would lose information. In my case, I support devices that need WEXT, thus disabling it in the configuration would not work. Logging one per application would entail a bit of work, but that would clear up the log spamming and work for me.
Wouldn't it be simpler to use custom rate limit parameters ? I see the defaults hardcoded in pr_warn_ratelimited() are 10 messages every 5 seconds before the rate limit triggers.
Changing them would require some layer busting, but it is still significantly simpler than caching names in an array.
