> I did a quick look and in wireless drivers some of the alloc_skb() > callers print an error and some fail silently. I think we should start > printing errors for all alloc_skb() calls. Thoughts? I think we don't always print an error because TCP protocol can guarantee reliability and packets lost are normal. Also in memory limited platforms it might be regular that fails allocating memory causing flooding log if we always print an error. Maybe print with rate limit is a choice? But this kind of log seems unnecessary and annoying to users.