From: Len Brown <lenb@kernel.org>
To: Simon Horman <horms@verge.net.au>
Cc: Roel Kluin <12o3l@tiscali.nl>,
tony.luck@intel.com, linux-ia64@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH with title] priority fix in acpi_map_lsapic() arch/ia64/kernel/acpi.c
Date: Tue, 4 Dec 2007 01:22:07 -0500 [thread overview]
Message-ID: <200712040122.07391.lenb@kernel.org> (raw)
In-Reply-To: <20071120065145.GB10490@verge.net.au>
Applied.
thanks,
-Len
On Tuesday 20 November 2007 01:51, Simon Horman wrote:
> On Thu, Nov 15, 2007 at 11:32:39PM +0100, Roel Kluin wrote:
> > As above should have been its title.
> >
> > Roel Kluin wrote:
> > > I have sent this patch before to lkml, but it appears it wasn't picked up. Also
> > > I have to admit this isn't tested. This is a patch against linus' tree.
> > >
> > > ACPI_MADT_ENABLED is defined 1 (include/acpi/actbl1.h 501)
> > > lapic_flags: an u32 of struct acpi_madt_local_sapic (include/acpi/actbl1.h 467)
> > > --
> > > '!' has a higher priority than '&', so as was
> > > this won't test the first bit, but rather evaluates to false for any non-zero
> > > lsapic->lapic_flags.
> > >
> > > Signed-off-by: Roel Kluin <12o3l@tiscali.nl>
>
> This looks correct to me, though I was curious to know why
> the problem wasn't manifesting in a bug. I investigated
> a bit and found that it seems that the only values
> lapic_flags currently takes are 0 and ACPI_MADT_ENABLED,
> so it turns out that the bogus logic actually gives the correct result
> (by chance).
>
> Acked-by: Simon Horman <horms@verge.net.au>
>
> > > ---
> > > diff --git a/arch/ia64/kernel/acpi.c b/arch/ia64/kernel/acpi.c
> > > index 3d45d24..7d78d22 100644
> > > --- a/arch/ia64/kernel/acpi.c
> > > +++ b/arch/ia64/kernel/acpi.c
> > > @@ -858,7 +858,7 @@ int acpi_map_lsapic(acpi_handle handle, int *pcpu)
> > > lsapic = (struct acpi_madt_local_sapic *)obj->buffer.pointer;
> > >
> > > if ((lsapic->header.type != ACPI_MADT_TYPE_LOCAL_SAPIC) ||
> > > - (!lsapic->lapic_flags & ACPI_MADT_ENABLED)) {
> > > + (!(lsapic->lapic_flags & ACPI_MADT_ENABLED))) {
> > > kfree(buffer.pointer);
> > > return -EINVAL;
> > > }
> > >
>
prev parent reply other threads:[~2007-12-04 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 22:03 [PATCH] Roel Kluin
2007-11-15 22:32 ` [PATCH with title] priority fix in acpi_map_lsapic() arch/ia64/kernel/acpi.c Roel Kluin
2007-11-20 6:51 ` Simon Horman
2007-12-04 6:22 ` Len Brown [this message]
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=200712040122.07391.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=12o3l@tiscali.nl \
--cc=horms@verge.net.au \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--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 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).