[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140318143759.04a892434d84a9fd3aa94262@linux-foundation.org>
Date: Tue, 18 Mar 2014 14:37:59 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Christoph Lameter <cl@...ux.com>
Cc: Grygorii Strashko <grygorii.strashko@...com>,
linux-arm <linux-arm-kernel@...ts.infradead.org>,
Tejun Heo <tj@...nel.org>, linux-kernel@...r.kernel.org,
Santosh Shilimkar <santosh.shilimkar@...com>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: [linux-next][regression] [PATCH] percpu: add preemption checks
to __this_cpu ops
On Tue, 18 Mar 2014 10:54:06 -0500 (CDT) Christoph Lameter <cl@...ux.com> wrote:
> On Tue, 18 Mar 2014, Grygorii Strashko wrote:
>
> > Any way, I can boot and console works fine with your change :)
> > Thanks.
>
> Ok here is the properly formatted patch:
>
>
> Subject: preemption_checks: Avoid snprintf before checking error conditions
>
> snprintf can cause hangs.
This is weird. How the heck can snprintf() fail if called too early?
All it does is shuffle chars around in memory. The only external
dependency I'm seeing is a WARN_ON() which presumably didn't trigger
anyway.
I'm suspecting a misdiagnosis here. Otherwise, we seriously need to
fix snprintf(), not work around it!
Also, what does "before checking error conditions" refer to? Does this
mean you know why snprintf() failed??
> Move the string processing into the function
> so that the string operations only occur when necessary after the
> conditions have been checked.
>
> Tested-by: Grygorii Strashko <grygorii.strashko@...com>
Grygorii, thanks for testing linux-next on unusual machines - it's most
helpful.
> Signed-off-by: Christoph Lameter <cl@...ux.com>
--
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