Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>, Liam <lgirdwood@gmail.com>
Cc: alsa-devel@alsa-project.org, gsantosh@codeaurora.org
Subject: Re: Question on compress offload framework memory corruption
Date: Sun, 5 Jan 2014 19:34:38 +0530	[thread overview]
Message-ID: <20140105140438.GX16227@intel.com> (raw)
In-Reply-To: <20131219105508.GV31886@sirena.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1215 bytes --]

On Thu, Dec 19, 2013 at 10:55:08AM +0000, Mark Brown wrote:
> On Wed, Dec 18, 2013 at 01:17:51PM -0000, gsantosh@codeaurora.org wrote:
> > Hi,
> > 
> > I have following questions in the compressed offload framework API.
> > 
> > static int soc_compr_set_params_fe(struct snd_compr_stream *cstream,
> > 					struct snd_compr_params *params)
> > {
> > ...
> > 	hw_params = kzalloc(sizeof(*hw_params), GFP_KERNEL);
> > 	if (hw_params == NULL)
> > 		return -ENOMEM;
> > /*1st question is, what is the use of above allocated memory I do not see
> > this being used in this function*/
> 
> The code you're quoting there isn't in mainline.  I've also added Vinod
> to the CCs, you probably want to include him in any discussion of the
> compressed API.
That's right, this is from DPCM compressed updated done by Liam, so he is the
best person to comment on this bit, and somehow his address in CC has gone bad,
i have added him in to list

But yes looking at the source, i agree that two are interlinked.
I guess we need to poupulate the hw_params and then use that to copy, that would
be the right thing to do here and yes this is not correct and not sure how this
is working...

-- 
~Vinod

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2014-01-05 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 13:17 Question on compress offload framework memory corruption gsantosh
2013-12-19  7:59 ` gsantosh
2013-12-19 10:42 ` Clemens Ladisch
2013-12-19 10:55 ` Mark Brown
2014-01-05 14:04   ` Vinod Koul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-03-04 22:19 Banajit Goswami
2014-03-05  7:51 ` 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=20140105140438.GX16227@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=gsantosh@codeaurora.org \
    --cc=lgirdwood@gmail.com \
    /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