> On 22 Jul 2015, at 14:04, Daniel Borkmann <dan...@iogearbox.net> wrote: > > On 07/22/2015 01:48 PM, David Laight wrote: >> From: Jamal Hadi Salim >>> Sent: 09 July 2015 11:38 >>> >>> In the newer kernels this message is extremely noisy. After a quick >>> discussion with Daniel it seems to me it will be very hard to get >>> existing apps that nobody is going to update to continue to work >>> (i.e no forward compat). And newer apps that desire to play in both >>> older kernels and new kernels will have to play some tricks to work >>> (i.e weak backward compatibility). These are good reasons >>> to totally get rid of this message. At minimal to neutre it. >>> The attached change tries to do that. However, if you had multiple >>> apps, you will only get warning for the first one. >> >> Never mind spanning the kernel log, there will be performance >> issues with systems that are sending significant amounts of SCTP data. >> I'm not sure you'll get 10000+/sec through the trace system. > > What do you mean by "trace system" (there's no backtrace)? > > Anyway, as previously stated, I doubt we'd get rid of the deprecated > SCTP uapi from the RFC any time soon, so, imho, we should just remove > these rate-limited messages altogether to stop spamming the klog ... ... and we will not remove it in FreeBSD either.
Best regards Michael > >> I'm going to have to find which version this trace went into and >> make sure we tell customers not to use the relevant kernel versions. >> >> David >> > > -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
