From: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
To: sreekuttan2156239@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
perex@perex.cz, tiwai@suse.com, tiwai@suse.de
Subject: [PATCH v2] ALSA: core: Fix info read handling
Date: Mon, 9 Nov 2026 08:59:22 +0000 [thread overview]
Message-ID: <20261109085922.3104-1-sreekuttan2156239@gmail.com> (raw)
In-Reply-To: <20261109080850.2726-1-sreekuttan2156239@gmail.com>
snd_info_entry_read() may invoke driver read callbacks with a
zero-length read when the requested count is zero.
Some callbacks perform zero-sized allocations, such as
vmalloc(0), which can trigger warnings and cause the read to
fail with -ENOMEM.
Return immediately when count is zero to avoid invoking driver
callbacks unnecessarily.
Also, store the callback result in a separate ssize_t variable
instead of reusing the size_t variable. This makes the signedness
explicit and avoids the unnecessary cast when checking whether
to update the file position.
Update the file position only when the callback returns a
positive number of bytes.
Signed-off-by: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
---
v2:
- Handle zero-length reads in snd_info_entry_read() by returning
early without invoking the driver callback.
- Clarify the commit message to describe the ssize_t change as a
signedness cleanup rather than claiming it fixes incorrectly
reported callback errors.
sound/core/info.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/sound/core/info.c b/sound/core/info.c
index c4d57d0809ad..42312136f76c 100644
--- a/sound/core/info.c
+++ b/sound/core/info.c
@@ -144,6 +144,7 @@ static ssize_t snd_info_entry_read(struct file *file, char __user *buffer,
struct snd_info_private_data *data = file->private_data;
struct snd_info_entry *entry = data->entry;
size_t size;
+ ssize_t ret;
loff_t pos;
pos = *offset;
@@ -151,13 +152,15 @@ static ssize_t snd_info_entry_read(struct file *file, char __user *buffer,
return -EIO;
if (pos >= entry->size)
return 0;
+ if (!count)
+ return 0;
size = entry->size - pos;
size = min(count, size);
- size = entry->c.ops->read(entry, data->file_private_data,
+ ret = entry->c.ops->read(entry, data->file_private_data,
file, buffer, size, pos);
- if ((ssize_t) size > 0)
- *offset = pos + size;
- return size;
+ if (ret > 0)
+ *offset = pos + ret;
+ return ret;
}
static ssize_t snd_info_entry_write(struct file *file, const char __user *buffer,
--
2.55.0
next prev parent reply other threads:[~2026-11-09 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 8:08 [PATCH] ALSA: core: Fix signedness issue in info read callback Sreeraj S Kurup
2026-11-09 8:59 ` Sreeraj S Kurup [this message]
2026-11-09 9:22 ` [PATCH v3] ALSA: core: Fix info read handling Sreeraj S Kurup
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=20261109085922.3104-1-sreekuttan2156239@gmail.com \
--to=sreekuttan2156239@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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®