From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0000389]: random buffer snd_output_t issues
Date: Thu, 15 Jul 2004 20:14:56 +0200 (CEST) [thread overview]
Message-ID: <20040715181456.CD3C519004@server.perex-int.cz> (raw)
A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000389
======================================================================
Reported By: Benjamin Otte
Assigned To:
======================================================================
Project: ALSA - lib
Bug ID: 389
Category: general
Reproducibility: always
Severity: crash
Priority: normal
Status: new
======================================================================
Date Submitted: 07-15-2004 20:09 CEST
Last Modified: 07-15-2004 20:14 CEST
======================================================================
Summary: random buffer snd_output_t issues
Description:
There are several issues with using a snd_output_t acquired from
snd_output_buffer_open(). These cause random segfaults because of
writing/reading invalid memory.
The attached patch fixes those issues.
======================================================================
----------------------------------------------------------------------
Benjamin Otte - 07-15-2004 20:14 CEST
----------------------------------------------------------------------
patch to fix the issues.
These include:
- snd_output_buffer_need might not resize the buffer to be big enough, if
huge sizes are required.
- calculating the needed buffer size does not take care of the terminating
null byte vsprintf puts at the end. So in rare cases, the buffer is
exactly one byte too small. Use vsnprintf instead to guard against these
problems.
- snd_output_buffer_print does not correct the size member for the number
of bytes added.
Bug History
Date Modified Username Field Change
======================================================================
07-15-04 20:09 Benjamin Otte New Bug
07-15-04 20:09 Benjamin Otte File Added: test-overwrite.c
07-15-04 20:14 Benjamin Otte Bugnote Added: 0001438
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
next reply other threads:[~2004-07-15 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 18:14 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-24 11:34 [ALSA - lib 0000389]: random buffer snd_output_t issues bugtrack
2004-07-20 15:36 noreply
2004-07-20 15:36 noreply
2004-07-15 18:09 noreply
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=20040715181456.CD3C519004@server.perex-int.cz \
--to=noreply@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.