All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the y2038 tree
Date: Thu, 14 Nov 2019 13:10:10 +0100	[thread overview]
Message-ID: <CAK8P3a19MuYrrk_TZq5Jz-4AH0U5NYX1=WZZHcdyD+G+Rz8n2A@mail.gmail.com> (raw)
In-Reply-To: <20191114153810.55d937af@canb.auug.org.au>

On Thu, Nov 14, 2019 at 5:38 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the y2038 tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> arch/powerpc/kernel/time.c: In function 'update_vsyscall':
> arch/powerpc/kernel/time.c:960:33: error: 'struct timespec64' has no member named 'sec'
>   960 |  vdso_data->stamp_xtime_sec = xt.sec;
>       |                                 ^
> arch/powerpc/kernel/time.c:961:34: error: 'struct timespec64' has no member named 'nsec'
>   961 |  vdso_data->stamp_xtime_nsec = xt.nsec;
>       |                                  ^
>
> Caused by commit
>
>   009a81339beb ("y2038: vdso: powerpc: avoid timespec references")
>
> I have added the following patch for today.
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Thu, 14 Nov 2019 15:28:13 +1100
> Subject: [PATCH] fix up for "y2038: vdso: powerpc: avoid timespec references"
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>

Folded into my patch, thanks!

> diff --git a/arch/powerpc/kernel/time.c b/arch/powerpc/kernel/time.c
> index ee9ba3a48c76..2d13cea13954 100644
> --- a/arch/powerpc/kernel/time.c
> +++ b/arch/powerpc/kernel/time.c
> @@ -957,8 +957,8 @@ void update_vsyscall(struct timekeeper *tk)
>         vdso_data->tb_to_xs = new_tb_to_xs;
>         vdso_data->wtom_clock_sec = tk->wall_to_monotonic.tv_sec;
>         vdso_data->wtom_clock_nsec = tk->wall_to_monotonic.tv_nsec;
> -       vdso_data->stamp_xtime_sec = xt.sec;
> -       vdso_data->stamp_xtime_nsec = xt.nsec;
> +       vdso_data->stamp_xtime_sec = xt.tv_sec;
> +       vdso_data->stamp_xtime_nsec = xt.tv_nsec;
>         vdso_data->stamp_sec_fraction = frac_sec;
>         smp_wmb();
>         ++(vdso_data->tb_update_count);

I was sure I had at least build-tested this, but looking at 'git reflog -p',
I only see the same broken version that never worked, so I clearly did not.

     Arnd

  reply	other threads:[~2019-11-14 12:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14  4:38 linux-next: build failure after merge of the y2038 tree Stephen Rothwell
2019-11-14 12:10 ` Arnd Bergmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-17  9:11 Stephen Rothwell
2018-12-17 12:49 ` Arnd Bergmann
2018-12-17 22:25   ` Steve French
2018-03-27  7:26 Stephen Rothwell
2018-03-16  2:25 Stephen Rothwell
2018-03-16  2:25 ` Stephen Rothwell
2018-03-16  5:23 ` Deepa Dinamani
2018-03-16  8:14   ` Arnd Bergmann
2018-03-17 23:13     ` Deepa Dinamani

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='CAK8P3a19MuYrrk_TZq5Jz-4AH0U5NYX1=WZZHcdyD+G+Rz8n2A@mail.gmail.com' \
    --to=arnd@arndb.de \
    --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 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.