linux-kernel - Re: Hard LOCKUP with 2.6.32.28 (maybe scheduler/tick related?)

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: <AANLkTi=V5JEi8DWev+mHh8K30cc5xPsy5hr1zS+QND23@mail.gmail.com>
Date:	Mon, 31 Jan 2011 15:21:27 +0100
From:	Sebastian Färber <faerber@...il.com>
To:	Don Zickus <dzickus@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Hard LOCKUP with 2.6.32.28 (maybe scheduler/tick related?)

Hi Don,

>
> Your attached 'crash' details had another stacktrace first.  That one
> shows the nmi_watchdog triggering because a spin_lock is spinning forever
> in 'd_real_path'.  I couldn't find that code in any upstream tree, then
> again I was too lazy to clone the stable trees.  So I don't know what the
> exact problem is, but if you look through the git history of 2.6.32.28 and
> revert things that relate to 'd_real_path', you can probably workaround
> the problem for now, until someone who knows that stuff better than me can
> give you a better answer.

Thanks for the pointer. The 'd_real_path' function is part of
grsecurity, i'll see if they
can help :-)

Regards,

Sebastian
--
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/