[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUUHXq-ZBYqgwitrC9Ek8LJZoK=bZQ8CbWppd8zJWx=F9w@mail.gmail.com>
Date: Sun, 30 Jun 2013 23:52:19 +0200
From: Sedat Dilek <sedat.dilek@...il.com>
To: Valdis.Kletnieks@...edu
Cc: Oleg Nesterov <oleg@...hat.com>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org,
Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Imre Deak <imre.deak@...el.com>,
Lukas Czerner <lczerner@...hat.com>,
Samuel Ortiz <samuel@...tiz.org>,
Wensong Zhang <wensong@...ux-vs.org>,
Simon Horman <horms@...ge.net.au>,
Julian Anastasov <ja@....bg>,
Ralf Baechle <ralf@...ux-mips.org>
Subject: Re: linux-next: Tree for Jun 28 [ BISECTED: rsyslog/imklog: High CPU
usage ]
On Sun, Jun 30, 2013 at 10:17 PM, <Valdis.Kletnieks@...edu> wrote:
> On Sun, 30 Jun 2013 20:19:45 +0200, Oleg Nesterov said:
>>
>> 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?
>
> I'm not Sedat, but I had the same problem with rsyslog going nuts,
> and I can confirm that the patch fixes the problem. (Had to hand-apply
> it, there was some difference of opinion regarding { } on an else)
>
I am... Legend :-).
Thanks for confirmation!
- Yes, it's you (every day Gmail says this to me) "Sedat" -
> Feel free to toss on a Tested-By: if this becomes a separate commit...
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists