From: Eric Paris <eparis@parisplace.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: linux-next: Tree for May 29 (__rdmsr_on_cpu() OOPS)
Date: Mon, 1 Jun 2009 15:55:22 -0400 [thread overview]
Message-ID: <7e0fb38c0906011255o25f2e852r6ba469c8345e8c77@mail.gmail.com> (raw)
In-Reply-To: <200905302137.57644.bzolnier@gmail.com>
On Sat, May 30, 2009 at 3:37 PM, Bartlomiej Zolnierkiewicz
<bzolnier@gmail.com> wrote:
> [ Borislav, feel free to fold it into the above change or replace by
> a more complete one if needed (there may be more rv fields needing
> initialization). ]
>
> From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> Subject: [PATCH] x86: MSR: fix __rdmsr_on_cpu() OOPS
>
> {rd,wr}msr_on_cpu() need to explicitly initalize rv.msrs
> (since rv is allocated on the stack).
>
> Cc: Borislav Petkov <borislav.petkov@amd.com>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Still broken in 0601, none of my systems will even boot without this patch.
Tested-by: Eric Paris <eparis@redhat.com>
> ---
> arch/x86/lib/msr.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> Index: b/arch/x86/lib/msr.c
> ===================================================================
> --- a/arch/x86/lib/msr.c
> +++ b/arch/x86/lib/msr.c
> @@ -44,6 +44,7 @@ int rdmsr_on_cpu(unsigned int cpu, u32 m
> int err;
> struct msr_info rv;
>
> + rv.msrs = NULL;
> rv.msr_no = msr_no;
> err = smp_call_function_single(cpu, __rdmsr_on_cpu, &rv, 1);
> *l = rv.reg.l;
> @@ -58,6 +59,7 @@ int wrmsr_on_cpu(unsigned int cpu, u32 m
> int err;
> struct msr_info rv;
>
> + rv.msrs = NULL;
> rv.msr_no = msr_no;
> rv.reg.l = l;
> rv.reg.h = h;
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2009-06-01 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 4:50 linux-next: Tree for May 29 Stephen Rothwell
2009-05-30 19:37 ` linux-next: Tree for May 29 (__rdmsr_on_cpu() OOPS) Bartlomiej Zolnierkiewicz
2009-06-01 19:55 ` Eric Paris [this message]
2009-06-02 14:13 ` Borislav Petkov
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=7e0fb38c0906011255o25f2e852r6ba469c8345e8c77@mail.gmail.com \
--to=eparis@parisplace.org \
--cc=borislav.petkov@amd.com \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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