From: Nikolay Borisov <nborisov@suse.com>
To: dsterba@suse.cz, Arnd Bergmann <arnd@arndb.de>,
Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
David Sterba <dsterba@suse.com>,
y2038@lists.linaro.org, Omar Sandoval <osandov@fb.com>,
Liu Bo <bo.li.liu@oracle.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] btrfs: use timespec64 for i_otime
Date: Wed, 20 Jun 2018 22:34:16 +0300 [thread overview]
Message-ID: <263b1bc6-0efb-8803-fb9a-68a1393d35b2@suse.com> (raw)
In-Reply-To: <20180620163804.GE24375@twin.jikos.cz>
On 20.06.2018 19:38, David Sterba wrote:
> On Wed, Jun 20, 2018 at 04:34:34PM +0200, Arnd Bergmann wrote:
>> While the regular inode timestamps all use timespec64 now, the
>> i_otime field is btrfs specific and still needs to be converted
>> to correctly represent times beyond 2038.
>>
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> This patch addresses the remaining type conversions, so I'm going to
> merge it, thanks.
>
Actually for the sake of consistency we might want to merge this series
altogether. As it stands we now use ktime_get_seconds and
ktime_get_real_seconds (from Allen's patch). I haven't dug to see what's
the difference (if any) between the two .
next prev parent reply other threads:[~2018-06-20 19:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 14:34 [PATCH 1/3] btrfs: use monotonic time for transaction handling Arnd Bergmann
2018-06-20 14:34 ` [PATCH 2/3] btrfs: use 64-bit timestamps for struct btrfs_dev_replace_item Arnd Bergmann
2018-06-20 14:36 ` David Sterba
2018-06-20 15:15 ` Arnd Bergmann
2018-06-20 14:34 ` [PATCH 3/3] btrfs: use timespec64 for i_otime Arnd Bergmann
2018-06-20 16:38 ` David Sterba
2018-06-20 19:34 ` Nikolay Borisov [this message]
2018-06-20 19:41 ` Arnd Bergmann
2018-06-21 8:23 ` Nikolay Borisov
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=263b1bc6-0efb-8803-fb9a-68a1393d35b2@suse.com \
--to=nborisov@suse.com \
--cc=arnd@arndb.de \
--cc=bo.li.liu@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@fb.com \
--cc=y2038@lists.linaro.org \
/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®