From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Steven Rostedt In-Reply-To: <1300386121.16880.359.camel@gandalf.stny.rr.com> References: <1300370936.16880.96.camel@gandalf.stny.rr.com> <1300380909.16880.264.camel@gandalf.stny.rr.com> <1300381340.6315.323.camel@edumazet-laptop> <1300386121.16880.359.camel@gandalf.stny.rr.com> Content-Type: text/plain; charset="ISO-8859-15" Date: Thu, 17 Mar 2011 14:32:50 -0400 Message-ID: <1300386770.16880.383.camel@gandalf.stny.rr.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: um: WARNING: at kernel/futex.c:786 __unqueue_futex To: Geert Uytterhoeven Cc: Eric Dumazet , richard -rw- weinberger , laijs@cn.fujitsu.com, LKML , user-mode-linux-devel@lists.sourceforge.net, dvhart@linux.intel.com List-ID: On Thu, 2011-03-17 at 14:22 -0400, Steven Rostedt wrote: > On Thu, 2011-03-17 at 18:43 +0100, Geert Uytterhoeven wrote: > > > I don't know. It's not clear to me if "WARN_ON_SMP(x)" should always return "x", > > or only on SMP? > > > > E.g. > > > > if (WARN_ON_SMP(x)) { > > // Should we get here if "x" is true? > > // Or only if CONFIG_SMP and "x" are both true? > > } > > > > The "Or only if CONFIG_SMP and "x" are both true. > > I'll update the change to add a comment about that. > We are the first user of this false return, as do { } while (0) doesn't return anything. I'll add a comment to explain the issue, but it makes sense to have it returns false on UNIPROCESSOR. -- Steve