linux-kernel - RE: pstore dump inside an nmi handler

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]

Message-ID: <987664A83D2D224EAE907B061CE93D5301E981AB56@orsmsx505.amr.corp.intel.com>
Date:	Fri, 8 Jul 2011 14:40:13 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Don Zickus <dzickus@...hat.com>
CC:	"mjg@...hat.com" <mjg@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: pstore dump inside an nmi handler

> Inside pstore_dump(), the first thing it tries to grab is a mutex_lock()
> (inside an nmi hander).  This seems to be the root cause of my problems.

Someone else pointed out that mutex_lock() is a problem here too. They
wondered whether spin_lock_irqsave() would work - or whether pstore
backends were allowed to sleep - to which I said I hoped they didn't,
but wasn't really sure what the future will hold.

So ... ideas (and patches) are most welcome.

-Tony


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