From: Andrew Lunn
Date: Sun, 16 Aug 2020 21:26:38 +0200
> It is possible to trigger this WARN_ON from user space by triggering a
> devlink snapshot with an ID which already exists. We don't need both
> -EEXISTS being reported and spamming the kernel log.
>
> Signed-off-by: Andrew Lunn
Applied,
With this patch applied, I no longer experience the kernel warning messages.
Tested-by: Chris Healy
On Sun, Aug 16, 2020 at 12:27 PM Andrew Lunn wrote:
>
> It is possible to trigger this WARN_ON from user space by triggering a
> devlink snapshot with an ID which already exists. We don't need bo
On Sun, Aug 16, 2020 at 09:26:38PM +0200, Andrew Lunn wrote:
> It is possible to trigger this WARN_ON from user space by triggering a
> devlink snapshot with an ID which already exists. We don't need both
> -EEXISTS being reported and spamming the kernel log.
Upps. Forgot the net-next in the subje
It is possible to trigger this WARN_ON from user space by triggering a
devlink snapshot with an ID which already exists. We don't need both
-EEXISTS being reported and spamming the kernel log.
Signed-off-by: Andrew Lunn
---
net/core/devlink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
