[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210928132902.1594277-1-aardelean@deviqon.com>
Date: Tue, 28 Sep 2021 16:29:02 +0300
From: Alexandru Ardelean <ardeleanalex@...il.com>
To: linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: ohad@...ery.com, bjorn.andersson@...aro.org,
mathieu.poirier@...aro.org,
Alexandru Ardelean <ardeleanalex@...il.com>
Subject: [PATCH] rpmsg: virtio_rpmsg_bus: use dev_warn_ratelimited for msg with no recipient
From: Alexandru Ardelean <ardeleanalex@...il.com>
Even though it may be user-space's fault for this error (some application
terminated or crashed without cleaning up it's endpoint), the rpmsg
communication should not overflow the syslog with too many messages.
A dev_warn_ratelimited() seems like a good alternative in case this can
occur.
Signed-off-by: Alexandru Ardelean <ardeleanalex@...il.com>
---
drivers/rpmsg/virtio_rpmsg_bus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c
index 8e49a3bacfc7..546f0fb66f1d 100644
--- a/drivers/rpmsg/virtio_rpmsg_bus.c
+++ b/drivers/rpmsg/virtio_rpmsg_bus.c
@@ -749,7 +749,7 @@ static int rpmsg_recv_single(struct virtproc_info *vrp, struct device *dev,
/* farewell, ept, we don't need you anymore */
kref_put(&ept->refcount, __ept_release);
} else
- dev_warn(dev, "msg received with no recipient\n");
+ dev_warn_ratelimited(dev, "msg received with no recipient\n");
/* publish the real size of the buffer */
rpmsg_sg_init(&sg, msg, vrp->buf_size);
--
2.31.1
Powered by blists - more mailing lists