linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiang Liu <jiang.liu@linux.intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Thomas Voegtle <tv@lio96.de>, Hudd <hedede.l@gmail.com>,
	Prakash Punnoor <prakash@punnoor.de>,
	Francois Romieu <romieu@fr.zoreil.com>,
	Dave Airlie <airlied@gmail.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	Len Brown <lenb@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Lv Zheng <lv.zheng@intel.com>
Subject: Re: [Debug 2/2] x86/PCI/ACPI: Relax ACPI resource descriptor checks to work around BIOS bugs
Date: Wed, 04 Mar 2015 10:29:22 +0800	[thread overview]
Message-ID: <54F66E02.5090408@linux.intel.com> (raw)
In-Reply-To: <CAErSpo6MtTj+DM0dtm0QxUXGV=rC7a0Sygs03sU0617mWO-DpA@mail.gmail.com>

On 2015/3/3 23:18, Bjorn Helgaas wrote:
> On Mon, Mar 2, 2015 at 10:25 PM, Jiang Liu <jiang.liu@linux.intel.com> wrote:
>> Some BIOSes report incorrect length for ACPI address space descriptors,
>> so relax the checks to avoid regressions.
>>
>> Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
> 
> It'd be nice to have a DSDT archived and referenced in this changelog
> for future reference.  This sounds similar to previous issues:
Hi all,
	Could anybody help to dump an ACPI table from those failure
systems so we could archive it?
Thanks!
Gerry

> 
> 3162b6f0c5e1 ("PNPACPI: truncate _CRS windows with _LEN > _MAX - _MIN + 1")
> d558b483d5a7 ("x86/PCI: truncate _CRS windows with _LEN > _MAX - _MIN + 1")
> f238b414a74a ("PNPACPI: compute Address Space length rather than using _LEN")
> 48728e077480 ("x86/PCI: compute Address Space length rather than using _LEN")
> 
> I assume your work fixes both these paths and avoids the issues we fixed above.
> 
>> ---
>>  drivers/acpi/resource.c |    4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c
>> index c723668e3e27..5589a6e2a023 100644
>> --- a/drivers/acpi/resource.c
>> +++ b/drivers/acpi/resource.c
>> @@ -42,8 +42,10 @@ static bool acpi_dev_resource_len_valid(u64 start, u64 end, u64 len, bool io)
>>          * CHECKME: len might be required to check versus a minimum
>>          * length as well. 1 for io is fine, but for memory it does
>>          * not make any sense at all.
>> +        * Note: some BIOSes report incorrect length for ACPI address space
>> +        * descriptor, so remove check of 'reslen == len' to avoid regression.
>>          */
>> -       if (len && reslen && reslen == len && start <= end)
>> +       if (len && reslen && start <= end)
>>                 return true;
>>
>>         pr_debug("ACPI: invalid or unassigned resource %s [%016llx - %016llx] length [%016llx]\n",
>> --
>> 1.7.10.4
>>

  reply	other threads:[~2015-03-04  2:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  4:25 [Debug 0/2] Fix regressions caused by commit 593669c2ac0f Jiang Liu
2015-03-03  4:25 ` [Debug 1/2] x86/PCI/ACPI: Ignore resources consumed by host bridge itself Jiang Liu
2015-03-03  4:25 ` [Debug 2/2] x86/PCI/ACPI: Relax ACPI resource descriptor checks to work around BIOS bugs Jiang Liu
2015-03-03 15:18   ` Bjorn Helgaas
2015-03-04  2:29     ` Jiang Liu [this message]
2015-03-04  2:58       ` Dave Airlie
2015-03-04 11:26       ` Thomas Voegtle
2015-03-04 16:05       ` Prakash Punnoor
2015-03-04 21:31       ` Hudd
2015-03-03  4:34 ` [Debug 0/2] Fix regressions caused by commit 593669c2ac0f Dave Airlie
2015-03-03  5:02   ` Jiang Liu
2015-03-03 17:19   ` Prakash Punnoor

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=54F66E02.5090408@linux.intel.com \
    --to=jiang.liu@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=hedede.l@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=marcel@holtmann.org \
    --cc=prakash@punnoor.de \
    --cc=rjw@rjwysocki.net \
    --cc=romieu@fr.zoreil.com \
    --cc=tglx@linutronix.de \
    --cc=tv@lio96.de \
    /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).