The kernel-doc for dma_buf_set_name() documents an -EBUSY return for the case where the dma-buf is already attached to devices. The function has no such path: it returns 0 on success, or the error from strndup_user().
kernel-doc does not validate prose, so scripts/kernel-doc does not report this. Signed-off-by: Hung-Chun Tseng <[email protected]> --- drivers/dma-buf/dma-buf.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.c index d504c636d..324f4f0c8 100644 --- a/drivers/dma-buf/dma-buf.c +++ b/drivers/dma-buf/dma-buf.c @@ -413,8 +413,8 @@ static __poll_t dma_buf_poll(struct file *file, poll_table *poll) * @buf: [in] A piece of userspace memory that contains the name of * the dma-buf. * - * Returns 0 on success. If the dma-buf buffer is already attached to - * devices, return -EBUSY. + * Returns 0 on success, or a negative error code from strndup_user() if the + * name cannot be copied in. * */ static long dma_buf_set_name(struct dma_buf *dmabuf, const char __user *buf) -- 2.43.0
