From: Breno Rodrigues Alves <breno3011alves@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Breno Rodrigues Alves <breno3011alves@gmail.com>
Subject: [PATCH] staging: axis-fifo: Fix three real issues
Date: Thu, 22 Oct 2026 18:53:49 -0300 [thread overview]
Message-ID: <20261022215349.87471-1-breno3011alves@gmail.com> (raw)
Fix three issues in the Xilinx AXI-Stream FIFO driver:
1. axis_fifo_debugfs_init() did not check the return value of
debugfs_create_dir(). When CONFIG_DEBUG_FS=n, the function
returns ERR_PTR(-ENODEV); passing it as a parent to
debugfs_create_file() triggers a WARN in the kernel debugfs
core. Bail out early if the directory was not created.
2. axis_fifo_read() returned -EINVAL when the user buffer was
smaller than the available data. The user argument is not
invalid - it is just too small - so return -ENOBUFS, which is
the canonical errno for that situation (see recv(2)).
3. axis_fifo_probe() filled in a 'struct resource *r_mem' pointer
that is never read. Pass NULL instead.
No functional change for the normal path.
Signed-off-by: Breno Rodrigues Alves <breno3011alves@gmail.com>
---
drivers/staging/axis-fifo/axis-fifo.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/axis-fifo/axis-fifo.c b/drivers/staging/axis-fifo/axis-fifo.c
index 3d358f919..c19cb68de 100644
--- a/drivers/staging/axis-fifo/axis-fifo.c
+++ b/drivers/staging/axis-fifo/axis-fifo.c
@@ -148,7 +148,7 @@ static ssize_t axis_fifo_read(struct file *f, char __user *buf,
words_available = bytes_available / sizeof(u32);
if (bytes_available > len) {
- ret = -EINVAL;
+ ret = -ENOBUFS;
goto err_flush_rx;
}
@@ -378,6 +378,8 @@ DEFINE_SHOW_ATTRIBUTE(axis_fifo_debugfs_regs);
static void axis_fifo_debugfs_init(struct axis_fifo *fifo)
{
fifo->debugfs_dir = debugfs_create_dir(dev_name(fifo->dt_device), NULL);
+ if (IS_ERR_OR_NULL(fifo->debugfs_dir))
+ return;
debugfs_create_file("regs", 0444, fifo->debugfs_dir, fifo,
&axis_fifo_debugfs_regs_fops);
@@ -428,7 +430,6 @@ static int axis_fifo_parse_dt(struct axis_fifo *fifo)
static int axis_fifo_probe(struct platform_device *pdev)
{
- struct resource *r_mem;
struct device *dev = &pdev->dev;
struct axis_fifo *fifo = NULL;
int rc = 0; /* error return value */
@@ -447,7 +448,7 @@ static int axis_fifo_probe(struct platform_device *pdev)
mutex_init(&fifo->read_lock);
mutex_init(&fifo->write_lock);
- fifo->base_addr = devm_platform_get_and_ioremap_resource(pdev, 0, &r_mem);
+ fifo->base_addr = devm_platform_get_and_ioremap_resource(pdev, 0, NULL);
if (IS_ERR(fifo->base_addr))
return PTR_ERR(fifo->base_addr);
--
2.56.0
next reply other threads:[~2026-10-22 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 21:53 Breno Rodrigues Alves [this message]
2026-10-23 6:08 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261022215349.87471-1-breno3011alves@gmail.com \
--to=breno3011alves@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®