From: sudarshan.bisht@nokia.com
To: alsa-devel@alsa-project.org
Subject: [PATCH] *** Fixed issues/defects reported by Coverity tool ***
Date: Thu, 17 Mar 2011 10:12:18 +0200 [thread overview]
Message-ID: <1300349539-32209-1-git-send-email-sudarshan.bisht@nokia.com> (raw)
From: Sudarshan <sudarshan.bisht@nokia.com>
Coverity Static Analysis helps developers find hard-to-spot,
yet potentially crash-causing defects early in the development phase,
reducing the cost,time, and risk of software errors.
This patch has a fix for conditions where 1) variable is used
evern after getting freed thus causing junk assignment and 2) double
free of memory.
Sudarshan (1):
alsa-lib: fixed coverity reported issues under "USE_AFTER_FREE"
checker.
src/control/control_hw.c | 1 +
src/mixer/mixer.c | 2 +-
2 files changed, 2 insertions(+), 1 deletions(-)
next reply other threads:[~2011-03-17 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 8:12 sudarshan.bisht [this message]
2011-03-17 8:12 ` [PATCH] alsa-lib: fixed coverity reported issues under "USE_AFTER_FREE" checker sudarshan.bisht
2011-03-17 11:22 ` Clemens Ladisch
2011-03-17 13:33 ` Sudarshan Bisht
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=1300349539-32209-1-git-send-email-sudarshan.bisht@nokia.com \
--to=sudarshan.bisht@nokia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).