linux-kernel - Re: Suspend/Resume bug in PCI layer wrt quirks

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: <20080515105426.24ee37d9@infradead.org>
Date:	Thu, 15 May 2008 10:54:26 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	len.brown@...el.com, "Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Suspend/Resume bug in PCI layer wrt quirks

On Thu, 15 May 2008 09:07:06 -0700
> > internally. ioremap()/iounmap() does a global tlb flush of course,
> > which includes doing an IPI to other cpus. However, during early
> > resume, interrupts are disabled, and it's not allowed to do a
> > IPI/global tlbflush with interrupts off...
> 
> Yeah I just got a similar report for quirk_vialatency().  But why are
> we only seeing these issues now?  Is our interrupt disabled check
> catching more stuff these days?

we're now more systematically collecting WARN_ON()'s.....
--
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/