All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
To: alsa-devel@alsa-project.org
Subject: [alsa-devel] [PATCH 0/2] [RFC] ASoC: topology: fix access beyond data
Date: Mon,  7 Oct 2019 10:41:31 +0200	[thread overview]
Message-ID: <20191007084133.7674-1-guennadi.liakhovetski@linux.intel.com> (raw)

This is likely incomplete, I haven't reviewed the whole of the
topology parsing code, and I haven't tested this yet - neither for
actually being a problem without these patches nor for fixing them.
This is a preview to give everybody a chance to showt out if I
misunderstood something and there isn't actually a problem to be
fixed.

Thanks
Guennadi

Guennadi Liakhovetski (2):
  ASoC: topology: protect against accessing beyond loaded topology data
  ASoC: topology: don't access beyond topology data

 sound/soc/soc-topology.c | 37 +++++++++++++++++++++++++++++--------
 1 file changed, 29 insertions(+), 8 deletions(-)

-- 
1.9.3

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

             reply	other threads:[~2019-10-07  8:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  8:41 Guennadi Liakhovetski [this message]
2019-10-07  8:41 ` [alsa-devel] [PATCH 1/2] ASoC: topology: protect against accessing beyond loaded topology data Guennadi Liakhovetski
2019-10-07 14:17   ` Pierre-Louis Bossart
2019-10-07 14:42     ` Guennadi Liakhovetski
2019-10-07  8:41 ` [alsa-devel] [PATCH 2/2] ASoC: topology: don't access beyond " Guennadi Liakhovetski
2019-10-07  9:13 ` [alsa-devel] [PATCH 0/2] [RFC] ASoC: topology: fix access beyond data Guennadi Liakhovetski

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=20191007084133.7674-1-guennadi.liakhovetski@linux.intel.com \
    --to=guennadi.liakhovetski@linux.intel.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 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.