From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org, lgirdwood@gmail.com
Subject: Re: [PATCH 2/5] ASoC: intel: log an error on double free
Date: Mon, 20 Oct 2014 18:44:13 +0530 [thread overview]
Message-ID: <20141020131413.GF28745@intel.com> (raw)
In-Reply-To: <s5hzjcrkmgy.wl-tiwai@suse.de>
On Mon, Oct 20, 2014 at 01:30:05PM +0200, Takashi Iwai wrote:
> At Mon, 20 Oct 2014 15:29:05 +0530,
> Vinod Koul wrote:
> >
> > the stream context should be freed only once on stream cleanup. If we ever
> > hit a chance that stream context is getting double freed, though not an
> > cause of panic as memory allocator can deal with this, we should still log
> > this to help in finding issues and debugging
> >
> > Signed-off-by: Vinod Koul <vinod.koul@intel.com>
> > ---
> > sound/soc/intel/sst/sst_drv_interface.c | 2 ++
> > 1 files changed, 2 insertions(+), 0 deletions(-)
> >
> > diff --git a/sound/soc/intel/sst/sst_drv_interface.c b/sound/soc/intel/sst/sst_drv_interface.c
> > index aadb0db..423c5ff 100644
> > --- a/sound/soc/intel/sst/sst_drv_interface.c
> > +++ b/sound/soc/intel/sst/sst_drv_interface.c
> > @@ -55,6 +55,8 @@ int free_stream_context(struct intel_sst_drv *ctx, unsigned int str_id)
> > if (ret)
> > sst_clean_stream(&ctx->streams[str_id]);
> > return ret;
> > + } else {
> > + dev_err(ctx->dev, "we tried to free stream context %d which was freed!!!", str_id);
>
> Missing line feed at the end of the string.
Thanks for pointing :)
--
~Vinod
>
>
> Takashi
>
>
> > }
> > return ret;
> > }
> > --
> > 1.7.0.4
> >
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >
--
next prev parent reply other threads:[~2014-10-20 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 9:59 [PATCH 0/5] ASoC: intel: fix to sst driver series Vinod Koul
2014-10-20 9:59 ` [PATCH 1/5] ASoC: intel: use __iowrite32_copy for 32 bit copy Vinod Koul
2014-10-20 11:29 ` Takashi Iwai
2014-10-20 13:14 ` Vinod Koul
2014-10-20 9:59 ` [PATCH 2/5] ASoC: intel: log an error on double free Vinod Koul
2014-10-20 11:30 ` Takashi Iwai
2014-10-20 13:14 ` Vinod Koul [this message]
2014-10-20 9:59 ` [PATCH 3/5] ASoC: intel: fix the kernldoc comment Vinod Koul
2014-10-20 9:59 ` [PATCH 4/5] ASoC: intel: explain why block not found isn't error always Vinod Koul
2014-10-20 9:59 ` [PATCH 5/5] ASoC: intel: use __iowrite32_copy for 32 bit copy Vinod Koul
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=20141020131413.GF28745@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.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