Hi Alex, > When -EAGAIN as return value for receive handling will do a retry of > parsing I can trigger a endless loop when iphc decompression e.g. > returns an errno because some missing function "-ENOTSUPP" or something > else. Somebody from outside can trigger an endless loop when sending a > an IPHC header which triggers this behaviour. > > NOTE: This really depends only if -EAGAIN means "try again to call the > receive handler with the skb". Sometimes we also drop (and kfree) the > skb, I think something is broken there... depends on the error branch. > When receiving failed simple free skb and return errno (which is not > -EAGAIN). I am lost on this comment, you need to explain this more and might actually want to put a comment in the code on this. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
