alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
	alsa-devel@alsa-project.org, broonie@kernel.org,
	"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Subject: Re: [PATCH v2 8/8] ASoC: Intel: Allocate for the mailbox with max size
Date: Tue, 19 May 2015 16:37:50 +0530	[thread overview]
Message-ID: <20150519110750.GL3140@localhost> (raw)
In-Reply-To: <s5hoalgzw5g.wl-tiwai@suse.de>

On Tue, May 19, 2015 at 12:42:03PM +0200, Takashi Iwai wrote:
> At Tue, 19 May 2015 15:00:40 +0530,
> Vinod Koul wrote:
> > 
> > From: "Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
> > 
> > Signed-off-by: Subhransu S. Prusty <subhransu.s.prusty@intel.com>
> > Signed-off-by: Vinod Koul <vinod.koul@intel.com>
> > ---
> >  sound/soc/intel/common/sst-ipc.c | 29 ++++++++++++++++++++++++++++-
> >  sound/soc/intel/common/sst-ipc.h |  4 ++--
> >  2 files changed, 30 insertions(+), 3 deletions(-)
> > 
> > diff --git a/sound/soc/intel/common/sst-ipc.c b/sound/soc/intel/common/sst-ipc.c
> > index a7699f35a8d2..a12c7bb08d3b 100644
> > --- a/sound/soc/intel/common/sst-ipc.c
> > +++ b/sound/soc/intel/common/sst-ipc.c
> > @@ -129,11 +129,31 @@ static int msg_empty_list_init(struct sst_generic_ipc *ipc)
> >  		return -ENOMEM;
> >  
> >  	for (i = 0; i < IPC_EMPTY_LIST_SIZE; i++) {
> > +		ipc->msg[i].tx_data = kzalloc(ipc->tx_data_max_size, GFP_KERNEL);
> > +		if (ipc->msg[i].tx_data == NULL)
> > +			goto free_mem;
> > +
> > +		ipc->msg[i].rx_data = kzalloc(ipc->rx_data_max_size, GFP_KERNEL);
> > +		if (ipc->msg[i].rx_data == NULL) {
> > +			kfree(ipc->msg[i].tx_data);
> > +			goto free_mem;
> > +		}
> > +
> >  		init_waitqueue_head(&ipc->msg[i].waitq);
> >  		list_add(&ipc->msg[i].list, &ipc->empty_list);
> 
> Wouldn't this leave stale linked list entries at error?
Yes it will, but this is happening at device probe, so the probe will fail
and device will no longer be usable. We do free the memory so shouldn't
leak.

-- 
~Vinod

  reply	other threads:[~2015-05-19 11:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  9:30 [PATCH v2 0/8] ASoC: Intel: refactor common SST IPC handling Vinod Koul
2015-05-19  9:30 ` [PATCH v2 1/8] ASoC: Intel: Create an ops to check for DSP busy Vinod Koul
2015-05-19  9:30 ` [PATCH v2 2/8] ASoC: Intel: Move the busy check to ops for Baytrail Vinod Koul
2015-05-19  9:30 ` [PATCH v2 3/8] ASoC: Intel: Move the busy check to ops for HSW Vinod Koul
2015-05-19  9:30 ` [PATCH v2 4/8] ASoC: Intel: Remove the direct register reference from common ipc Vinod Koul
2015-05-19  9:30 ` [PATCH v2 5/8] ASoC: Intel: Allow to configure max size for mailbox data Vinod Koul
2015-05-19  9:30 ` [PATCH v2 6/8] ASoC: Intel: Initialize max mailbox size for baytrail Vinod Koul
2015-05-19  9:30 ` [PATCH v2 7/8] ASoC: Intel: Initialize max mailbox size for haswell Vinod Koul
2015-05-22 18:23   ` Mark Brown
2015-05-19  9:30 ` [PATCH v2 8/8] ASoC: Intel: Allocate for the mailbox with max size Vinod Koul
2015-05-19 10:42   ` Takashi Iwai
2015-05-19 11:07     ` Vinod Koul [this message]
2015-05-21 21:14 ` [PATCH v2 0/8] ASoC: Intel: refactor common SST IPC handling Liam Girdwood

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=20150519110750.GL3140@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.com \
    --cc=subhransu.s.prusty@intel.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;
as well as URLs for NNTP newsgroup(s).