Anyway, the obvious "fix" should be just to drop WARN_ON(). It makes no sense to trigger a kernel WARNING with stack trace for the data that can be provided externally. It could be at most a debug message.