From: Arnd Bergmann <arnd@arndb.de>
To: John Stultz <john.stultz@linaro.org>
Cc: Jesper Nilsson <jesper.nilsson@axis.com>,
Thomas Gleixner <tglx@linutronix.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
lkml <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Michael Kerrisk <mtk@man7.org>,
Miroslav Lichvar <mlichvar@redhat.com>,
Arnd Bergmann <arnd.bergmann@linaro.org>
Subject: Re: [RESEND PATCH] timerfd: Allow TFD_TIMER_CANCEL_ON_SET with relative timeouts
Date: Tue, 20 Oct 2015 10:18:22 +0200 [thread overview]
Message-ID: <27613722.NGRuyuj3GB@wuerfel> (raw)
In-Reply-To: <CALAqxLVS+NBpz63d3bkQO5yv9gebuotjBdimb2o8X1KitSEqHA@mail.gmail.com>
On Monday 19 October 2015 11:53:25 John Stultz wrote:
>
> But yea. At the same time I get you want to avoid user-pain like in
> the case of the badly initialized RTC, but in that case would
> returning 0 for RTC reads greater then y2038 on 32 bit systems be a
> more sane fix?
I like that idea. In theory we could go further and check that the RTC
is somewhere between 2015 and 2037 (or higher on 64-bit systems) but
return 0 (1970) for anything that is outside of that range. That might
have side-effects for users that have a legitimate reason to backdate
their clocks though.
Arnd
next prev parent reply other threads:[~2015-10-20 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 8:25 [RESEND PATCH] timerfd: Allow TFD_TIMER_CANCEL_ON_SET with relative timeouts Jesper Nilsson
2015-10-19 18:53 ` John Stultz
2015-10-20 7:36 ` Miroslav Lichvar
2015-10-20 8:18 ` Arnd Bergmann [this message]
2015-10-20 8:59 ` Jesper Nilsson
2015-10-20 11:07 ` Arnd Bergmann
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=27613722.NGRuyuj3GB@wuerfel \
--to=arnd@arndb.de \
--cc=arnd.bergmann@linaro.org \
--cc=jesper.nilsson@axis.com \
--cc=john.stultz@linaro.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=mtk@man7.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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