public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tejun Heo <tj@kernel.org>, Daniel Vetter <daniel.vetter@ffwll.ch>,
	Imre Deak <imre.deak@intel.com>,
	Lukas Czerner <lczerner@redhat.com>,
	Samuel Ortiz <samuel@sortiz.org>,
	Wensong Zhang <wensong@linux-vs.org>,
	Simon Horman <horms@verge.net.au>, Julian Anastasov <ja@ssi.bg>,
	Ralf Baechle <ralf@linux-mips.org>,
	Valdis.Kletnieks@vt.edu
Subject: Re: linux-next: Tree for Jun 28 [ BISECTED: rsyslog/imklog: High CPU usage ]
Date: Sun, 30 Jun 2013 20:19:45 +0200	[thread overview]
Message-ID: <20130630181945.GA5171@redhat.com> (raw)
In-Reply-To: <CA+icZUXo=Z4gDfCMvLqRQDq_fpNAq+UqtUw=jrU=3=kVZP-2+A@mail.gmail.com>

Andrew, please drop these

	wait-introduce-wait_event_commonwq-condition-state-timeout.patch
	wait-introduce-prepare_to_wait_event.patch

patches again. I'll send v3 although it really looks like I should
never try to touch wait.h.

On 06/29, Sedat Dilek wrote:
>
> As this all did not show me what caused the problem I started a
> git-bisect session.
>
> This revealed the following culprit commit:
>
>      commit bb1f30cb7d3ba21098f0ee7e0382160ba2599a43
>      "wait: introduce wait_event_common(wq, condition, state, timeout)"

Heh. First of all, I am really sorry.

Not only "__wait_no_timeout(tout) ?:" was wrong, I didn't bother
to recheck this logic even after I got the "warning: the omitted
middle operand in ?:" reports.

Sedat, thanks you very much! Any chance you can try the patch below?

Oleg.


--- a/include/linux/wait.h
+++ b/include/linux/wait.h
@@ -191,12 +191,8 @@ wait_queue_head_t *bit_waitqueue(void *, int);
 	for (;;) {							\
 		__ret = prepare_to_wait_event(&wq, &__wait, state);	\
 		if (condition) {					\
-			__ret = __wait_no_timeout(tout);		\
-			if (!__ret) {					\
-				__ret = __tout;				\
-				if (!__ret)				\
-					__ret = 1;			\
-			}						\
+			__ret = __wait_no_timeout(tout) ? 0 :		\
+							(__tout ?: 1);	\
 			break;						\
 		}							\
 									\
@@ -217,16 +213,10 @@ wait_queue_head_t *bit_waitqueue(void *, int);
 #define wait_event_common(wq, condition, state, tout)			\
 ({									\
 	long __ret;							\
-	if (condition) {						\
-		__ret = __wait_no_timeout(tout);			\
-		if (!__ret) {						\
-			__ret = tout;					\
-			if (!__ret)					\
-				__ret = 1;				\
-		}							\
-	} else {							\
+	if (condition)							\
+		__ret = __wait_no_timeout(tout) ? 0 : ((tout) ?: 1);	\
+	else								\
 		__ret = __wait_event_common(wq, condition, state, tout);\
-	}								\
 	__ret;								\
 })
 

  parent reply	other threads:[~2013-06-30 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-29 21:44 linux-next: Tree for Jun 28 [ BISECTED: rsyslog/imklog: High CPU usage ] Sedat Dilek
2013-06-30 11:50 ` Sedat Dilek
2013-06-30 18:19 ` Oleg Nesterov [this message]
2013-06-30 20:17   ` Valdis.Kletnieks
2013-06-30 21:52     ` Sedat Dilek
2013-06-30 21:49   ` Sedat Dilek
2013-07-01  6:58   ` Stephen Rothwell
2013-07-02 10:15   ` Sedat Dilek
2013-07-02 22:37     ` Oleg Nesterov
2013-07-03  7:24       ` Sedat Dilek

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=20130630181945.GA5171@redhat.com \
    --to=oleg@redhat.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=horms@verge.net.au \
    --cc=imre.deak@intel.com \
    --cc=ja@ssi.bg \
    --cc=lczerner@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=samuel@sortiz.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tj@kernel.org \
    --cc=wensong@linux-vs.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