linux-kernel - Re: [tip:sched/urgent] sched: Fix __schedule_bug() output when called from an interrupt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4F74662A.7040704@tilera.com>
Date:	Thu, 29 Mar 2012 09:39:54 -0400
From:	Chris Metcalf <cmetcalf@...era.com>
To:	<mingo@...nel.org>, <hpa@...or.com>,
	<linux-kernel@...r.kernel.org>, <satyam@...radead.org>,
	<peterz@...radead.org>, <cmetcalf@...era.com>,
	<tglx@...utronix.de>, <sboyd@...eaurora.org>
CC:	<linux-tip-commits@...r.kernel.org>
Subject: Re: [tip:sched/urgent] sched: Fix __schedule_bug() output when called
 from an interrupt

On 3/29/2012 3:16 AM, tip-bot for Stephen Boyd wrote:
> Commit-ID:  6135fc1eb4b1c9ae5f535507ed59591bab51e630
> Gitweb:     http://git.kernel.org/tip/6135fc1eb4b1c9ae5f535507ed59591bab51e630
> Author:     Stephen Boyd <sboyd@...eaurora.org>
> AuthorDate: Wed, 28 Mar 2012 17:10:47 -0700
> Committer:  Ingo Molnar <mingo@...nel.org>
> CommitDate: Thu, 29 Mar 2012 08:34:45 +0200
>
> sched: Fix __schedule_bug() output when called from an interrupt
>
> If schedule is called from an interrupt handler __schedule_bug()
> will call show_regs() with the registers saved during the
> interrupt handling done in do_IRQ(). This means we'll see the
> registers and the backtrace for the process that was interrupted
> and not the full backtrace explaining who called schedule().
>
> This is due to 838225b ("sched: use show_regs() to improve
> __schedule_bug() output", 2007-10-24) which improperly assumed
> that get_irq_regs() would return the registers for the current
> stack because it is being called from within an interrupt
> handler. Simply remove the show_reg() code so that we dump a
> backtrace for the interrupt handler that called schedule().
>
> [ I ran across this when I was presented with a scheduling while
>   atomic log with a stacktrace pointing at spin_unlock_irqrestore().
>   It made no sense and I had to guess what interrupt handler could
>   be called and poke around for someone calling schedule() in an
>   interrupt handler. A simple test of putting an msleep() in
>   an interrupt handler works better with this patch because you
>   can actually see the msleep() call in the backtrace. ]
>
> Also-reported-by: Chris Metcalf <cmetcalf@...era.com>
> Signed-off-by: Stephen Boyd <sboyd@...eaurora.org>
> Cc: Satyam Sharma <satyam@...radead.org>
> Cc: Peter Zijlstra <peterz@...radead.org>
> Link: http://lkml.kernel.org/r/1332979847-27102-1-git-send-email-sboyd@codeaurora.org
> Signed-off-by: Ingo Molnar <mingo@...nel.org>

Acked-by: Chris Metcalf <cmetcalf@...era.com>

We have been using this same exact patch internally for a while now, and by
a curious fluke of timing, I sent email to Ingo and to Satyam Sharma
pointing out that we really should re-look at the original change just
yesterday :-)

-- 
Chris Metcalf, Tilera Corp.
http://www.tilera.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/