From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: stackprotector tree build failure
Date: Wed, 22 Oct 2008 06:32:27 +0200 [thread overview]
Message-ID: <20081022043227.GA31413@elte.hu> (raw)
In-Reply-To: <20081022131124.a572b11f.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> kernel/fork.c: In function 'copy_process':
> kernel/fork.c:1026: error: 'struct task_struct' has no member named 'default_timer_slack_ns'
> kernel/fork.c:1026: error: 'struct task_struct' has no member named 'timer_slack_ns'
>
> Caused by commit 929c12f25feeec881fd67eaa9b551f98588a2931 ("manual merge
> of stackprotector") which introduced the above line.
>
> I applied the following patch.
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Wed, 22 Oct 2008 13:09:17 +1100
> Subject: [PATCH] stackprotector: fix up bad merge
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> kernel/fork.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/fork.c b/kernel/fork.c
> index 194dc04..3bc1f86 100644
> --- a/kernel/fork.c
> +++ b/kernel/fork.c
> @@ -1023,8 +1023,6 @@ static struct task_struct *copy_process(unsigned long clone_flags,
> p->prev_utime = cputime_zero;
> p->prev_stime = cputime_zero;
>
> - p->default_timer_slack_ns = current->timer_slack_ns;
> -
> #ifdef CONFIG_DETECT_SOFTLOCKUP
> p->last_switch_count = 0;
> p->last_switch_timestamp = 0;
> --
> 1.5.6.5
thanks Stephen!
This seems to have been caused by a git-rerere bug - it mis-matched a
timers tree conflict resolution. I cleared out that resolution (it had
nothing to do with stackprotector), re-did the conflict resolution
(which was about overlapping additions of header files), and pushed out
a new stackprotector tree - the delta below has the expected result.
Ingo
diff --git a/kernel/fork.c b/kernel/fork.c
index 194dc04..3bc1f86 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -1023,8 +1023,6 @@ static struct task_struct *copy_process(unsigned long clone_flags,
p->prev_utime = cputime_zero;
p->prev_stime = cputime_zero;
- p->default_timer_slack_ns = current->timer_slack_ns;
-
#ifdef CONFIG_DETECT_SOFTLOCKUP
p->last_switch_count = 0;
p->last_switch_timestamp = 0;
next prev parent reply other threads:[~2008-10-22 4:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 2:11 linux-next: stackprotector tree build failure Stephen Rothwell
2008-10-22 4:32 ` Ingo Molnar [this message]
2008-10-22 7:21 ` Stephen Rothwell
2008-10-22 7:29 ` Ingo Molnar
2008-10-22 8:27 ` Stephen Rothwell
2008-10-22 8:31 ` Stephen Rothwell
2008-10-22 8:31 ` Ingo Molnar
2008-10-22 17:41 ` Johannes Schindelin
2008-10-22 23:54 ` Stephen Rothwell
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=20081022043227.GA31413@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--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 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).