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] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 18 Jan 2011 14:47:21 +0100
From:	Matthias Merz <linux@...z-ka.de>
To:	Brian Gerst <brgerst@...il.com>
Cc:	Matthias Merz <linux@...z-ka.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: Regression in linux 2.6.37: failure on remount / (ext4) rw

Hello together,

Am Mo, 17.01.2011 07:32 schrieb Brian Gerst
> On Fri, Jan 14, 2011 at 9:04 AM, Matthias Merz <linux@...z-ka.de> wrote:
> > git bisect now told me "22d4cd4c4dce6d7b7d9a7e396aa4f87fe7a649b1 is the
> > first bad commit", which is titled: "x86-32: Allocate irq stacks
> > seperate from percpu area".
> > I reverted this change (and following 47f19a0814 due to #defines) and
> > waited over the night until this morning. That revert really seems to
> > fix my problem. So maybe in my special case something goes wrong with
> > the new method?
> 
> Does this patch fix the problem?
> 
> Subject: [PATCH] x86: Clear irqstack thread_info
> 
> Make sure that the thread_info part of the irqstack is initialized
> to zeroes.
> 
> Signed-off-by: Brian Gerst <brgerst@...il.com>


Yes, I tried booting three times with that patch enabled, the last time
this morning after power-down over night; all seems fine so far.
Thank you very much for the prompt fix!


Yours
Matthias Merz

-- 
"I hope to die before I *have* to use Microsoft Word."
     - Donald E. Knuth, 2001-10-02 in Tübingen.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ