From: Ingo Molnar <mingo@elte•hu>
To: Masami Hiramatsu <mhiramat@redhat•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Thomas Gleixner <tglx@linutronix•de>,
"H. Peter Anvin" <hpa@zytor•com>,
linux-next@vger•kernel.org
Subject: Re: linux-next: tracing tree build failure
Date: Thu, 26 Mar 2009 08:54:10 +0100 [thread overview]
Message-ID: <20090326075410.GA31669@elte.hu> (raw)
In-Reply-To: <49CADC4F.2030002@redhat.com>
* Masami Hiramatsu <mhiramat@redhat•com> wrote:
> Hi Stephen,
>
> Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next build (x86_64 allmodconfig) failed like this:
> >
> > arch/x86/kernel/kprobes.c: In function 'trampoline_handler':
> > arch/x86/kernel/kprobes.c:697: error: 'struct pt_regs' has no member named 'gs'
> >
> > Caused by commit b9dad0d2955db059cd92c81c37ddcbef0abc8bf8 ("x86:
> > kretprobe-booster interrupt emulation code fix"). 64bit appears to not
> > have a gs in its pt_regs.
>
> Oh, that was fixed on linux-2.6-tip tree...
>
> http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=commit;h=fee039a1d05c6e0f71b0fe270d847742a02d56c4
I have pushed out a new tree for linux-next, to pick up this fix.
Ingo
next prev parent reply other threads:[~2009-03-26 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 1:14 linux-next: tracing tree build failure Stephen Rothwell
2009-03-26 1:37 ` Masami Hiramatsu
2009-03-26 7:54 ` Ingo Molnar [this message]
2009-03-26 8:04 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-03-10 0:55 Stephen Rothwell
2009-03-10 1:49 ` Tejun Heo
2009-03-10 9:10 ` Ingo Molnar
2009-03-10 2:16 ` KOSAKI Motohiro
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=20090326075410.GA31669@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=hpa@zytor$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mhiramat@redhat$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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