From: Masami Hiramatsu <mhiramat@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: tracing tree build failure
Date: Wed, 25 Mar 2009 21:37:19 -0400 [thread overview]
Message-ID: <49CADC4F.2030002@redhat.com> (raw)
In-Reply-To: <20090326121459.197d346a.sfr@canb.auug.org.au>
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 used the version of this tree that was in next-20090325 for today.
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-03-26 1:37 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 [this message]
2009-03-26 7:54 ` Ingo Molnar
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=49CADC4F.2030002@redhat.com \
--to=mhiramat@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.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 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.