From: Matthew Wilcox <matthew@wil.cx>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-pci@atrey.karlin.mff.cuni.cz,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
Kernel development list <linux-kernel@vger.kernel.org>,
Adam Belay <abelay@MIT.EDU>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: Bug in PCI core
Date: Fri, 13 Oct 2006 10:49:33 -0600 [thread overview]
Message-ID: <20061013164933.GD11633@parisc-linux.org> (raw)
In-Reply-To: <1160759349.25218.62.camel@localhost.localdomain>
On Fri, Oct 13, 2006 at 06:09:09PM +0100, Alan Cox wrote:
> Ar Gwe, 2006-10-13 am 12:34 -0400, ysgrifennodd Adam Belay:
> > I agree this needs to be fixed. However, as I previously mentioned,
> > this isn't the right place to attack the problem. Remember, this wasn't
> > originally a kernel regression. Rather it's a workaround for a known
>
> It's a kernel regression. It used to be reliable to read X resource
> addresses at any time.
No it didn't. It's undefined behaviour to perform *any* PCI config
access to the device while it's doing a D-state transition. It may have
happened to work with the chips you tried it with, but more likely you
never hit that window because X simply didn't try to do that.
> > Finally, it's worth noting that this issue is really a corner-case, and
> > in most systems it's extremely rare that even incorrect userspace apps
> > would have any issue.
>
> Except just occasionally and randomly in the field, probably almost
> undebuggable and irreproducable - the very worst conceivable kind of
> bug.
Indeed. Only now we have software producing it, rather than hardware
producing it. That's actually an improvement I think, since it forces
awareness of the issue.
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <matthew@wil.cx>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Adam Belay <abelay@MIT.EDU>,
Arjan van de Ven <arjan@infradead.org>,
Alan Stern <stern@rowland.harvard.edu>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Greg KH <greg@kroah.com>,
linux-pci@atrey.karlin.mff.cuni.cz,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Bug in PCI core
Date: Fri, 13 Oct 2006 10:49:33 -0600 [thread overview]
Message-ID: <20061013164933.GD11633@parisc-linux.org> (raw)
In-Reply-To: <1160759349.25218.62.camel@localhost.localdomain>
On Fri, Oct 13, 2006 at 06:09:09PM +0100, Alan Cox wrote:
> Ar Gwe, 2006-10-13 am 12:34 -0400, ysgrifennodd Adam Belay:
> > I agree this needs to be fixed. However, as I previously mentioned,
> > this isn't the right place to attack the problem. Remember, this wasn't
> > originally a kernel regression. Rather it's a workaround for a known
>
> It's a kernel regression. It used to be reliable to read X resource
> addresses at any time.
No it didn't. It's undefined behaviour to perform *any* PCI config
access to the device while it's doing a D-state transition. It may have
happened to work with the chips you tried it with, but more likely you
never hit that window because X simply didn't try to do that.
> > Finally, it's worth noting that this issue is really a corner-case, and
> > in most systems it's extremely rare that even incorrect userspace apps
> > would have any issue.
>
> Except just occasionally and randomly in the field, probably almost
> undebuggable and irreproducable - the very worst conceivable kind of
> bug.
Indeed. Only now we have software producing it, rather than hardware
producing it. That's actually an improvement I think, since it forces
awareness of the issue.
next prev parent reply other threads:[~2006-10-13 16:49 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 20:41 Bug in PCI core Alan Stern
2006-10-13 1:01 ` [linux-pm] " Benjamin Herrenschmidt
2006-10-13 8:50 ` Adam Belay
2006-10-13 8:50 ` [linux-pm] " Adam Belay
2006-10-13 9:16 ` Benjamin Herrenschmidt
2006-10-13 9:16 ` [linux-pm] " Benjamin Herrenschmidt
2006-10-13 9:31 ` Martin Mares
2006-10-13 9:31 ` [linux-pm] " Martin Mares
2006-10-13 12:25 ` Benjamin Herrenschmidt
2006-10-13 14:29 ` Alan Stern
2006-10-13 14:29 ` [linux-pm] " Alan Stern
2006-10-13 15:26 ` Alan Cox
2006-10-13 15:29 ` Arjan van de Ven
2006-10-13 16:06 ` Alan Cox
2006-10-13 16:34 ` Adam Belay
2006-10-13 16:34 ` [linux-pm] " Adam Belay
2006-10-13 16:36 ` Matthew Wilcox
2006-10-13 17:09 ` Alan Cox
2006-10-13 17:09 ` [linux-pm] " Alan Cox
2006-10-13 16:49 ` Matthew Wilcox [this message]
2006-10-13 16:49 ` Matthew Wilcox
2006-10-13 17:34 ` Alan Cox
2006-10-13 17:34 ` [linux-pm] " Alan Cox
2006-10-13 17:13 ` Arjan van de Ven
2006-10-13 17:13 ` [linux-pm] " Arjan van de Ven
2006-10-13 17:57 ` Alan Stern
2006-10-13 17:57 ` [linux-pm] " Alan Stern
2006-10-13 19:18 ` Matthew Wilcox
2006-10-13 20:59 ` Alan Stern
2006-10-13 20:59 ` [linux-pm] " Alan Stern
2006-10-13 19:30 ` Adam Belay
2006-10-13 19:30 ` [linux-pm] " Adam Belay
2006-10-13 23:00 ` Benjamin Herrenschmidt
2006-10-13 23:00 ` [linux-pm] " Benjamin Herrenschmidt
2006-10-14 2:33 ` Alan Stern
2006-10-14 2:33 ` [linux-pm] " Alan Stern
2006-10-14 3:04 ` Roland Dreier
2006-10-14 3:04 ` Roland Dreier
2006-10-14 3:07 ` Matthew Wilcox
2006-10-14 3:19 ` Bill Randle
2006-10-14 3:19 ` [linux-pm] " Bill Randle
2006-10-14 5:47 ` Greg KH
2006-10-14 5:47 ` [linux-pm] " Greg KH
2006-10-13 17:01 ` Adam Belay
2006-10-13 17:01 ` [linux-pm] " Adam Belay
2006-10-13 16:40 ` Adam Belay
2006-10-13 16:40 ` [linux-pm] " Adam Belay
2006-10-13 20:48 ` Pavel Machek
2006-10-14 5:34 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061013164933.GD11633@parisc-linux.org \
--to=matthew@wil.cx \
--cc=abelay@MIT.EDU \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux-pm@lists.osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.