linux-kernel - Re: [PATCH 8/8] ALSA: add new 32-bit layout for snd_pcm_mmap

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: <s5hefj2i2vz.wl-tiwai@suse.de>
Date:   Thu, 26 Apr 2018 14:11:12 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     "Arnd Bergmann" <arnd@...db.de>
Cc:     "kbuild test robot" <lkp@...el.com>, <kbuild-all@...org>,
        <alsa-devel@...a-project.org>,
        "Arvind Yadav" <arvind.yadav.cs@...il.com>,
        "Bhumika Goyal" <bhumirks@...il.com>,
        "Liam Girdwood" <lgirdwood@...il.com>,
        <gudishax.kranthikumar@...el.com>,
        "Guneshwor Singh" <guneshwor.o.singh@...el.com>,
        <hardik.t.shah@...el.com>, <jeeja.kp@...el.com>,
        "Naveen M" <naveen.m@...el.com>, <subhransu.s.prusty@...el.com>,
        "Vinod Koul" <vinod.koul@...el.com>,
        "Mark Brown" <broonie@...nel.org>,
        "Ingo Molnar" <mingo@...nel.org>,
        "Baolin Wang" <baolin.wang@...aro.org>,
        "Dan Carpenter" <dan.carpenter@...cle.com>,
        "Jaroslav Kysela" <perex@...ex.cz>,
        "Takashi Sakamoto" <o-takashi@...amocchi.jp>,
        "Fabian Frederick" <fabf@...net.be>,
        "SF Markus Elfring" <elfring@...rs.sourceforge.net>,
        "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 8/8] ALSA: add new 32-bit layout for snd_pcm_mmap_status/control

On Thu, 26 Apr 2018 13:31:17 +0200,
Arnd Bergmann wrote:
> 
> On Thu, Apr 26, 2018 at 1:25 PM, kbuild test robot <lkp@...el.com> wrote:
> > Hi Arnd,
> >
> > I love your patch! Perhaps something to improve:
> >
> > [auto build test WARNING on v4.17-rc2]
> > [cannot apply to sound/for-next asoc/for-next arm-soc/for-next next-20180426]
> > [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
> >
> > url:    https://github.com/0day-ci/linux/commits/Baolin-Wang/Fix-year-2038-issue-for-sound-subsystem/20180426-010145
> > reproduce:
> >         # apt-get install sparse
> >         make ARCH=x86_64 allmodconfig
> >         make C=1 CF=-D__CHECK_ENDIAN__
> >
> >
> > sparse warnings: (new ones prefixed by >>)
> >
> >    sound/firewire/motu/motu-pcm.c:35:29: sparse: expression using sizeof(void)
> >    sound/firewire/motu/motu-pcm.c:35:29: sparse: expression using sizeof(void)
> >    sound/firewire/motu/motu-pcm.c:36:29: sparse: expression using sizeof(void)
> >    sound/firewire/motu/motu-pcm.c:36:29: sparse: expression using sizeof(void)
> >    sound/firewire/motu/motu-pcm.c:65:32: sparse: expression using sizeof(void)
> >    sound/firewire/motu/motu-pcm.c:65:32: sparse: expression using sizeof(void)
> >    sound/firewire/motu/motu-pcm.c:66:32: sparse: expression using sizeof(void)
> >    sound/firewire/motu/motu-pcm.c:66:32: sparse: expression using sizeof(void)
> >    sound/firewire/motu/motu-pcm.c:92:36: sparse: expression using sizeof(void)
> >    sound/firewire/motu/motu-pcm.c:92:36: sparse: expression using sizeof(void)
> >    sound/firewire/motu/motu-pcm.c:93:36: sparse: expression using sizeof(void)
> >    sound/firewire/motu/motu-pcm.c:93:36: sparse: expression using sizeof(void)
> >>> sound/firewire/motu/motu-pcm.c:204:50: sparse: restricted snd_pcm_state_t degrades to integer
> >    sound/firewire/motu/motu-pcm.c:223:50: sparse: restricted snd_pcm_state_t degrades to integer
> >    sound/firewire/motu/motu-pcm.c:238:50: sparse: restricted snd_pcm_state_t degrades to integer
> >    sound/firewire/motu/motu-pcm.c:254:50: sparse: restricted snd_pcm_state_t degrades to integer
> 
> From what I can tell, these are all existing driver problems, no idea why we now
> have one more warning than before.

The only marked one is new, and others are already present in the
current code.  You can ignore these sparse warnings.


thanks,

Takashi