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]

Date:	Fri, 16 May 2008 22:16:30 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>, Greg KH <greg@...ah.com>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	len.brown@...el.com, Shaohua Li <shaohua.li@...el.com>
Subject: Re: Suspend/Resume bug in PCI layer wrt quirks

On Friday, 16 of May 2008, Jesse Barnes wrote:
> On Thursday, May 15, 2008 12:51 pm Rafael J. Wysocki wrote:
> > Some quirks should be called with interrupt disabled, we can't directly
> > call them in .resume_early. Also the patch introduces
> > pci_fixup_resume_early and pci_fixup_suspend, which matches current
> > device core callbacks (.suspend/.resume_early).
> >
> > TBD: Somebody knows why we need quirk resume should double check if a
> > quirk should be called in resume or resume_early. I changed some per my
> > understanding, but can't make sure I fixed all.
> >
> > Signed-off-by: Shaohua Li <shaohua.li@...el.com>
> 
> I applied this one to linux-next, it should fix some of the problems people 
> have been seeing at least...

Well, that will collide with
pm-new-suspend-and-hibernation-callbacks-for-pci-bus-type.patch
in the Greg's tree.

Greg, perhaps it's better if you drop it and I'll send an updated version to
Jesse?  That will make his tree dependent on yours, but that will be okay,
won't it?

Thanks,
Rafael
--
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/