All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, yang.a.fang@intel.com,
	lgirdwood@gmail.com, Carlo Caione <carlo@endlessm.com>,
	Carlo Caione <carlo@caione.org>,
	linux@endlessm.com
Subject: Re: [PATCH v2] ASoC: cht_bsw_rt5645: Fix writing to string literal
Date: Thu, 3 Mar 2016 17:02:56 +0530	[thread overview]
Message-ID: <20160303113255.GL11154@localhost> (raw)
In-Reply-To: <20160226021210.GE18327@sirena.org.uk>


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

On Fri, Feb 26, 2016 at 11:12:10AM +0900, Mark Brown wrote:
> On Tue, Feb 23, 2016 at 09:50:20AM +0100, Carlo Caione wrote:
> > From: Carlo Caione <carlo@endlessm.com>
> > 
> > We cannot use strcpy() to write to a const char * location. This is
> > causing a 'BUG: unable to handle kernel paging request' error at boot
> > when using the cht-bsw-rt5645 driver.
> > 
> > With this patch we also fix a wrong indexing in the driver where the
> > codec_name of the wrong dai_link is being overwritten.
> 
> So how was the original code tested then...?

I know systems using this are shipping so surprised to see this.

Carlo cna you please tell me the configuration where it is seen.

Also would be worth mentioning here that Pierre is working on a super fix
for this which involves removing this code and getting the right IDs from
BIOS, so we wont need this code.

Thanks
-- 
~Vinod

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

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



  reply	other threads:[~2016-03-03 11:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23  8:50 [PATCH v2] ASoC: cht_bsw_rt5645: Fix writing to string literal Carlo Caione
2016-02-26  2:12 ` Mark Brown
2016-03-03 11:32   ` Vinod Koul [this message]
2016-03-03 12:47     ` Carlo Caione
2016-03-03 16:11     ` Pierre-Louis Bossart
2016-03-03 16:16       ` Carlo Caione
2016-02-26  2:46 ` Applied "ASoC: cht_bsw_rt5645: Fix writing to string literal" to the asoc tree Mark Brown

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=20160303113255.GL11154@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=carlo@caione.org \
    --cc=carlo@endlessm.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux@endlessm.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=yang.a.fang@intel.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 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.