alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: kbuild-all@01.org, clemens@ladisch.de, tiwai@suse.de,
	vaishali.thakkar@oracle.com, alsa-devel@alsa-project.org,
	stable@vger.kernel.org, ffado-devel@lists.sf.net
Subject: Re: [alsa-devel] [PATCH 2/2] ALSA: firewire-tascam: accessing to user space outside spinlock
Date: Sat, 27 Aug 2016 05:30:20 +0800	[thread overview]
Message-ID: <201608270559.Z5M5aXML%fengguang.wu@intel.com> (raw)
In-Reply-To: <1472244609-31830-3-git-send-email-o-takashi@sakamocchi.jp>

[-- Attachment #1: Type: text/plain, Size: 2329 bytes --]

Hi Takashi,

[auto build test WARNING on sound/for-next]
[also build test WARNING on v4.8-rc3 next-20160825]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]

url:    https://github.com/0day-ci/linux/commits/Takashi-Sakamoto/ALSA-fireworks-accessing-to-user-space-outside-spinlock/20160827-045250
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next
config: tile-allyesconfig (attached as .config)
compiler: tilegx-linux-gcc (GCC) 4.6.2
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=tile 

All warnings (new ones prefixed by >>):

   sound/firewire/tascam/tascam-hwdep.c: In function 'hwdep_read':
>> sound/firewire/tascam/tascam-hwdep.c:24:8: warning: missing braces around initializer [-Wmissing-braces]
   sound/firewire/tascam/tascam-hwdep.c:24:8: warning: (near initialization for 'event.common') [-Wmissing-braces]

vim +24 sound/firewire/tascam/tascam-hwdep.c

     8	
     9	/*
    10	 * This codes give three functionality.
    11	 *
    12	 * 1.get firewire node information
    13	 * 2.get notification about starting/stopping stream
    14	 * 3.lock/unlock stream
    15	 */
    16	
    17	#include "tascam.h"
    18	
    19	static long hwdep_read(struct snd_hwdep *hwdep, char __user *buf, long count,
    20			       loff_t *offset)
    21	{
    22		struct snd_tscm *tscm = hwdep->private_data;
    23		DEFINE_WAIT(wait);
  > 24		union snd_firewire_event event = {0};
    25	
    26		spin_lock_irq(&tscm->lock);
    27	
    28		while (!tscm->dev_lock_changed) {
    29			prepare_to_wait(&tscm->hwdep_wait, &wait, TASK_INTERRUPTIBLE);
    30			spin_unlock_irq(&tscm->lock);
    31			schedule();
    32			finish_wait(&tscm->hwdep_wait, &wait);

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 45493 bytes --]

  reply	other threads:[~2016-08-26 21:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 20:50 [PATCH 0/2] ALSA: fireworks/firewire-tascam: accessing to user space outside spinlock Takashi Sakamoto
2016-08-26 20:50 ` [PATCH 1/2] ALSA: fireworks: " Takashi Sakamoto
2016-08-26 21:34   ` [alsa-devel] " kbuild test robot
2016-08-27  1:50     ` Takashi Sakamoto
2016-08-26 20:50 ` [PATCH 2/2] ALSA: firewire-tascam: " Takashi Sakamoto
2016-08-26 21:30   ` kbuild test robot [this message]
2016-08-29 17:32 ` [PATCH 0/2] ALSA: fireworks/firewire-tascam: " Vaishali Thakkar
2016-08-29 22:02   ` Takashi Sakamoto

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=201608270559.Z5M5aXML%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=ffado-devel@lists.sf.net \
    --cc=kbuild-all@01.org \
    --cc=o-takashi@sakamocchi.jp \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=vaishali.thakkar@oracle.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;
as well as URLs for NNTP newsgroup(s).