From: David Sterba <dsterba@suse.cz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
David Sterba <dsterba@suse.com>, Qu Wenruo <wqu@suse.com>,
Nikolay Borisov <nborisov@suse.com>,
Anand Jain <anand.jain@oracle.com>,
Liu Bo <bo.liu@linux.alibaba.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] [v2] btrfs: use monotonic time for transaction handling
Date: Thu, 21 Jun 2018 19:24:40 +0200 [thread overview]
Message-ID: <20180621172440.GT24375@twin.jikos.cz> (raw)
In-Reply-To: <20180621160420.139575-1-arnd@arndb.de>
On Thu, Jun 21, 2018 at 06:04:05PM +0200, Arnd Bergmann wrote:
> The transaction times were changed to ktime_get_real_seconds to avoid
> the y2038 overflow, but they still have a minor problem when they go
> backwards or jump due to settimeofday() or leap seconds.
>
> This changes the transaction handling to instead use ktime_get_seconds(),
> which returns a CLOCK_MONOTONIC timestamp that has neither of those
> problems.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> v2: Rebased on top of an earlier patch by Allen Pais, which
> also obsoleted the original patch 2/3
1 and 2 added to patch queue, thanks.
prev parent reply other threads:[~2018-06-21 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 16:04 Arnd Bergmann
2018-06-21 16:04 ` [PATCH 2/2] [v2] btrfs: use timespec64 for i_otime Arnd Bergmann
2018-06-21 16:09 ` Nikolay Borisov
2018-06-21 16:06 ` [PATCH 1/2] [v2] btrfs: use monotonic time for transaction handling Nikolay Borisov
2018-06-21 17:24 ` David Sterba [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=20180621172440.GT24375@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=arnd@arndb.de \
--cc=bo.liu@linux.alibaba.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=wqu@suse.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®