All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Andreas Schwab <schwab@suse.de>,
	"Luck, Tony" <tony.luck@intel.com>,
	"Brown, Len" <len.brown@intel.com>,
	linux-acpi@vger.kernel.org, linux-ia64@vger.kernel.org,
	Andrew Morton <akpm@osdl.org>,
	efocht@hpce.nec.com
Subject: Re: [PATCH] ACPI: fix vendor resource length computation
Date: Wed, 15 Feb 2006 18:49:48 +0100	[thread overview]
Message-ID: <43F369BC.9050604@suse.de> (raw)
In-Reply-To: <971FCB6690CD0E4898387DBF7552B90E045AACFA@orsmsx403.amr.corp.intel.com>

Moore, Robert wrote:
> I think the original code may have been attempting to subtract off the
> size of the descriptor header to obtain the length of the vendor data
> bytes. However, something like a global replace may have broken it.
> 
Thanks, this one fixes the mem corruption.
Unaligned access messages still remain...


   Thomas

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Renninger <trenn@suse.de>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Andreas Schwab <schwab@suse.de>,
	"Luck, Tony" <tony.luck@intel.com>,
	"Brown, Len" <len.brown@intel.com>,
	linux-acpi@vger.kernel.org, linux-ia64@vger.kernel.org,
	Andrew Morton <akpm@osdl.org>,
	efocht@hpce.nec.com
Subject: Re: [PATCH] ACPI: fix vendor resource length computation
Date: Wed, 15 Feb 2006 17:49:48 +0000	[thread overview]
Message-ID: <43F369BC.9050604@suse.de> (raw)
In-Reply-To: <971FCB6690CD0E4898387DBF7552B90E045AACFA@orsmsx403.amr.corp.intel.com>

Moore, Robert wrote:
> I think the original code may have been attempting to subtract off the
> size of the descriptor header to obtain the length of the vendor data
> bytes. However, something like a global replace may have broken it.
> 
Thanks, this one fixes the mem corruption.
Unaligned access messages still remain...


   Thomas

  reply	other threads:[~2006-02-15 17:49 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15  0:04 [PATCH] ACPI: fix vendor resource length computation Moore, Robert
2006-02-15  0:04 ` Moore, Robert
2006-02-15 17:49 ` Thomas Renninger [this message]
2006-02-15 17:49   ` Thomas Renninger
  -- strict thread matches above, loose matches on Subject: below --
2006-03-15 17:14 some new unaligned access while booting ia64 (HP rx2620) Moore, Robert
2006-03-15 17:14 ` Moore, Robert
2006-03-15 15:47 Moore, Robert
2006-03-15 15:47 ` Moore, Robert
2006-03-15 16:49 ` Bjorn Helgaas
2006-03-15 16:49   ` Bjorn Helgaas
2006-02-16 22:54 [PATCH] ACPI: fix vendor resource length computation Moore, Robert
2006-02-16 22:54 ` Moore, Robert
2006-02-15 19:05 Luck, Tony
2006-02-15 19:05 ` Luck, Tony
2006-02-16  8:59 ` Thomas Renninger
2006-02-16  8:59   ` Thomas Renninger
2006-02-15 18:38 Moore, Robert
2006-02-15 18:38 ` Moore, Robert
2006-02-14 23:25 Moore, Robert
2006-02-14 23:25 ` Moore, Robert
2006-02-14 23:34 ` Bjorn Helgaas
2006-02-14 23:34   ` Bjorn Helgaas
2006-02-11  0:39 some new unaligned access while booting ia64 (HP rx2620) Luck, Tony
2006-02-11  0:39 ` Luck, Tony
2006-02-11 12:21 ` Robin Holt
2006-02-11 12:21   ` Robin Holt
2006-02-10 23:58 Luck, Tony
2006-02-10 23:58 ` Luck, Tony
2006-02-10 23:31 Moore, Robert
2006-02-10 23:31 ` Moore, Robert
2006-02-13 18:51 ` Thomas Renninger
2006-02-13 18:51   ` Thomas Renninger
2006-02-13 22:33   ` Bjorn Helgaas
2006-02-13 22:33     ` Bjorn Helgaas
2006-02-13 22:57     ` Andreas Schwab
2006-02-13 22:57       ` Andreas Schwab
2006-02-14  0:22       ` Bjorn Helgaas
2006-02-14  0:22         ` Bjorn Helgaas
2006-02-14 23:13         ` [PATCH] ACPI: fix vendor resource length computation Bjorn Helgaas
2006-02-14 23:13           ` Bjorn Helgaas
2006-02-14 23:19           ` Bjorn Helgaas
2006-02-14 23:19             ` Bjorn Helgaas
2006-02-10 23:25 some new unaligned access while booting ia64 (HP rx2620) Luck, Tony
2006-02-10 23:25 ` Luck, Tony
2006-02-10 23:15 Moore, Robert
2006-02-10 23:15 ` Moore, Robert
2006-02-10 23:07 Moore, Robert
2006-02-10 23:07 ` Moore, Robert
2006-02-10 22:58 Luck, Tony
2006-02-10 22:58 ` Luck, Tony
2006-02-11 21:25 ` Bjorn Helgaas
2006-02-11 21:25   ` Bjorn Helgaas
2006-02-10 21:56 Moore, Robert
2006-02-10 21:56 ` Moore, Robert
2006-02-10 21:54 Luck, Tony
2006-02-10 21:54 ` Luck, Tony
2006-02-10 21:19 Moore, Robert
2006-02-10 21:19 ` Moore, Robert
2006-02-10 21:15 Luck, Tony
2006-02-10 21:15 ` Luck, Tony
2006-02-10 20:11 Moore, Robert
2006-02-10 20:11 ` Moore, Robert
2006-02-09 23:43 Moore, Robert
2006-02-09 23:43 ` Moore, Robert
2006-02-10  2:07 ` Thomas Renninger
2006-02-10  2:07   ` Thomas Renninger
2006-02-09 21:15 Luck, Tony
2006-02-09 21:15 ` Luck, Tony
2006-02-09 21:04 Luck, Tony
2006-02-09 21:04 ` Luck, Tony
2006-02-09 20:55 Moore, Robert
2006-02-09 20:55 ` Moore, Robert
2006-02-09 20:44 Luck, Tony
2006-02-09 20:44 ` Luck, Tony
2006-02-09 16:56 Moore, Robert
2006-02-09 16:56 ` Moore, Robert
2006-02-02 22:28 Moore, Robert
2006-02-02 22:28 ` Moore, Robert
2006-02-02 19:46 Luck, Tony
2006-02-02 19:46 ` Luck, Tony
2006-03-14 23:59 ` Bjorn Helgaas
2006-03-14 23:59   ` Bjorn Helgaas

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=43F369BC.9050604@suse.de \
    --to=trenn@suse.de \
    --cc=akpm@osdl.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=efocht@hpce.nec.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=robert.moore@intel.com \
    --cc=schwab@suse.de \
    --cc=tony.luck@intel.com \
    /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.