linux-kernel - Re: [PATCH] panic, vt: do not force oops output when panic

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]

Date:	Sat, 16 Jul 2011 00:17:21 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Mandeep Singh Baines <msb@...omium.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Huang Ying <ying.huang@...el.com>,
	Andi Kleen <ak@...ux.intel.com>,
	Hugh Dickins <hughd@...gle.com>, Olaf Hering <olaf@...fle.de>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Dave Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] panic, vt: do not force oops output when panic_timeout
 < 0

On Fri, 15 Jul 2011 14:39:27 -0700
Mandeep Singh Baines <msb@...omium.org> wrote:

> Alan Cox (alan@...rguk.ukuu.org.uk) wrote:
> > > a serial port. When I disabled the serial out, my machine started to
> > > get wedged on a panic. I guess screen_unblank was in bust_spinlocks
> > > for a reason. It probably bust some spin_locks somewhere.
> > 
> > No something else is wrong here. The console panic should be reliably
> > breaking the locks but a quick test of taking the console lock and BUG()
> > on a current kernel shows something has broken this.
> > 
> 
> Root caused to the issue I reported earlier with unblank_screen:
> 
> http://lkml.org/lkml/2011/6/20/394

Thanks - I missed that at the time and I'll take a look at it.
--
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/