lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAErzpmsg9fi0-ukHG13-dy2r02892h+oPXmtsusCbu-xLzazFQ@mail.gmail.com>
Date:   Tue, 22 Aug 2017 22:15:32 +0800
From:   Donglin Peng <dolinux.peng@...il.com>
To:     Mark Brown <broonie@...nel.org>
Cc:     Jeffy Chen <jeffy.chen@...k-chips.com>,
        linux-kernel@...r.kernel.org, dgreid@...omium.org,
        Heiko Stübner <heiko@...ech.de>,
        briannorris@...omium.org, mengdong.lin@...ux.intel.com,
        mka@...omium.org, lars@...afoo.de, dianders@...omium.org,
        Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
        Takashi Iwai <tiwai@...e.com>,
        Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH v5 2/9] ASoC: soc-core: Allow searching dai driver name in snd_soc_find_dai

On Tue, Aug 22, 2017 at 10:02 PM, Mark Brown <broonie@...nel.org> wrote:
> On Tue, Aug 22, 2017 at 09:24:32PM +0800, Donglin Peng wrote:
>
>> In case that dai->driver->name is NULL, strcmp(dai->driver->name,
>> dlc->dai_name) will cause segmentation fault.
>> so I think that we can change it as the follows:
>
> We should be already verifying that drivers have a name, we assume one
> elsewhere.

But I can't find any codes that set or check dai_driver->name in
function snd_soc_register_codec or snd_soc_register_component.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ