mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Salyzyn <salyzyn@android.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
	Chiawei Wang <chiaweiwang@google.com>,
	stable@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>
Subject: Re: [PATCH] lib/vdso: use CLOCK_REALTIME_COARSE for time()
Date: Thu, 11 Jun 2020 12:47:24 -0700	[thread overview]
Message-ID: <7147FC30-F9B4-4261-B2C1-08688A4E0D2B@android.com> (raw)
In-Reply-To: <878sgt1jo2.fsf@nanos.tec.linutronix.de>

On Jun 11, 2020, at 12:34 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> 
> Mark Salyzyn <salyzyn@android.com> writes:
>> From: Chiawei Wang <chiaweiwang@google.com>
>> 
>> CLOCK_REALTIME in vdso data won't be updated if
>> __arch_use_vsyscall() returns false.
> 
> Errm!
> 
> # git grep __arch_use_vsyscall
> #
> 
> Aside of that update_vsyscall() updates CLOCK_REALTIME data
> unconditionally. No idea what this patch is solving.
> 
>> Cc: stable@vger.kernel.org # 5.4+
> 
> This # 5.4+ is pointless. You really want to add a fixes tag which pin
> points the commit which introduced the wreckage.
> 
> But thats moot as this is not fixing anything not even in 5.4.
> 
> I assume this was developed against some Frankenkernel which has a messy
> backport or a snapshot of some development version of that vdso stuff.

Yes, problem code was removed with 52338415cf4d4064ae6b8dd972dadbda841da4fa not applied.

4.19 back port without time namespaces, chip vendor using __arch_use_vsyscall to solve a chip errata.

> 
> Not that I want to know, but please make sure that something you send my
> way makes sense on sane kernels.
> 
> Oh well.
> 
> Thanks,
> 
>        tglx

Sorry for your troubles.

Sincerely — Mark Salyzyn


      reply	other threads:[~2020-06-11 19:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 15:57 Mark Salyzyn
2020-06-11 19:34 ` Thomas Gleixner
2020-06-11 19:47   ` Mark Salyzyn [this message]

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=7147FC30-F9B4-4261-B2C1-08688A4E0D2B@android.com \
    --to=salyzyn@android.com \
    --cc=chiaweiwang@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincenzo.frascino@arm.com \
    /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

all inboxes | Powered by JetHome®