linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: kbuild-all@01.org, mingo@kernel.org, peterz@infradead.org,
	oleg@redhat.com, linux-kernel@vger.kernel.org, dave@stgolabs.net,
	Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH 1/2] sched: Introduce rcuwait machinery
Date: Fri, 23 Dec 2016 03:27:15 +0800	[thread overview]
Message-ID: <201612230340.HsWsZdiI%fengguang.wu@intel.com> (raw)
In-Reply-To: <1482426096-12792-2-git-send-email-dave@stgolabs.net>

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

Hi Davidlohr,

[auto build test ERROR on tip/auto-latest]
[also build test ERROR on v4.9 next-20161222]
[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/Davidlohr-Bueso/sched-Introduce-rcuwait/20161223-020109
config: i386-randconfig-s1-201651 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

Note: the linux-review/Davidlohr-Bueso/sched-Introduce-rcuwait/20161223-020109 HEAD 9e9d238f94d5aa8e348e7e70585533fe0dbd373b builds fine.
      It only hurts bisectibility.

All error/warnings (new ones prefixed by >>):

>> kernel/exit.c:285:29: warning: 'struct rcuwait' declared inside parameter list will not be visible outside of this definition or declaration
    void rcuwait_trywake(struct rcuwait *w)
                                ^~~~~~~
   In file included from include/linux/srcu.h:33:0,
                    from include/linux/notifier.h:15,
                    from include/linux/memory_hotplug.h:6,
                    from include/linux/mmzone.h:751,
                    from include/linux/gfp.h:5,
                    from include/linux/mm.h:9,
                    from kernel/exit.c:7:
   kernel/exit.c: In function 'rcuwait_trywake':
>> kernel/exit.c:308:26: error: dereferencing pointer to incomplete type 'struct rcuwait'
     task = rcu_dereference(w->task);
                             ^
   include/linux/rcupdate.h:606:10: note: in definition of macro '__rcu_dereference_check'
     typeof(*p) *________p1 = (typeof(*p) *__force)lockless_dereference(p); \
             ^
   include/linux/rcupdate.h:786:28: note: in expansion of macro 'rcu_dereference_check'
    #define rcu_dereference(p) rcu_dereference_check(p, 0)
                               ^~~~~~~~~~~~~~~~~~~~~
>> kernel/exit.c:308:9: note: in expansion of macro 'rcu_dereference'
     task = rcu_dereference(w->task);
            ^~~~~~~~~~~~~~~

vim +308 kernel/exit.c

   279		if (!sighand)
   280			return NULL;
   281	
   282		return task;
   283	}
   284	
 > 285	void rcuwait_trywake(struct rcuwait *w)
   286	{
   287		struct task_struct *task;
   288	
   289		rcu_read_lock();
   290	
   291		/*
   292		 * Order condition vs @task, such that everything prior to the load
   293		 * of @task is visible. This is the condition as to why the user called
   294		 * rcuwait_trywake() in the first place. Pairs with set_current_state()
   295		 * barrier (A) in rcuwait_wait_event().
   296		 *
   297		 *    WAIT                WAKE
   298		 *    [S] tsk = current	  [S] cond = true
   299		 *        MB (A)	      MB (B)
   300		 *    [L] cond		  [L] tsk
   301		 */
   302		smp_rmb(); /* (B) */
   303	
   304		/*
   305		 * Avoid using task_rcu_dereference() magic as long as we are careful,
   306		 * see comment in rcuwait_wait_event() regarding ->exit_state.
   307		 */
 > 308		task = rcu_dereference(w->task);
   309		if (task)
   310			wake_up_process(task);
   311		rcu_read_unlock();

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33607 bytes --]

  reply	other threads:[~2016-12-22 19:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 17:01 [PATCH 0/2] sched: Introduce rcuwait Davidlohr Bueso
2016-12-22 17:01 ` [PATCH 1/2] sched: Introduce rcuwait machinery Davidlohr Bueso
2016-12-22 19:27   ` kbuild test robot [this message]
2017-01-03 23:20     ` Davidlohr Bueso
2016-12-22 19:55   ` kbuild test robot
2017-01-16  1:32   ` Davidlohr Bueso
2017-01-17 17:41     ` Oleg Nesterov
2016-12-22 17:01 ` [PATCH 2/2] locking/percpu-rwsem: Replace waitqueue with rcuwait Davidlohr Bueso
2017-01-09 18:26 ` [PATCH 0/2] sched: Introduce rcuwait Davidlohr Bueso
2017-01-10 18:35   ` Oleg Nesterov
2017-01-10 19:37     ` Davidlohr Bueso
2017-01-11 15:22 [PATCH v2 " Davidlohr Bueso
2017-01-11 15:22 ` [PATCH 1/2] sched: Introduce rcuwait machinery Davidlohr Bueso

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=201612230340.HsWsZdiI%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=dave@stgolabs.net \
    --cc=dbueso@suse.de \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.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 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).