From: Artem Bityutskiy <dedekind1@gmail.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Matt Fleming <matt.fleming@intel.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Seth Forshee <seth.forshee@canonical.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/PCI: setup data may be in highmem
Date: Sat, 08 Jun 2013 14:15:46 +0300 [thread overview]
Message-ID: <1370690146.2938.64.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1369215782-32697-1-git-send-email-matt@console-pimps.org>
On Wed, 2013-05-22 at 10:43 +0100, Matt Fleming wrote:
> From: Matt Fleming <matt.fleming@intel.com>
>
> pcibios_add_device() assumes that the physical addresses stored in
> setup_data are accessible via the direct kernel mapping, and that
> calling phys_to_virt() is valid. This isn't guaranteed to be true on x86
> where the direct mapping range is much smaller than on x86-64.
>
> Calling phys_to_virt() on a highmem address results in the following,
Fixes paging request oops for me as well, thanks! Would you please add a
-stable tag to this patch?
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-06-08 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 9:43 [PATCH] x86/PCI: setup data may be in highmem Matt Fleming
2013-05-23 22:46 ` H. Peter Anvin
2013-05-24 14:38 ` Bjorn Helgaas
2013-05-28 11:36 ` Matt Fleming
2013-05-28 16:31 ` Bjorn Helgaas
2013-05-28 16:48 ` Matthew Garrett
2013-05-28 17:28 ` Bjorn Helgaas
2013-06-05 14:15 ` Matt Fleming
2013-06-05 17:10 ` Bjorn Helgaas
2013-06-08 11:15 ` Artem Bityutskiy [this message]
2013-06-08 11:14 ` Bityutskiy, Artem
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=1370690146.2938.64.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=mjg59@srcf.ucam.org \
--cc=seth.forshee@canonical.com \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).