linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Eric Sandeen'" <sandeen@sandeen.net>
Cc: "'fsdevel'" <linux-fsdevel@vger.kernel.org>
Subject: RE: [PATCH 0/2] exfat: timestamp fixes
Date: Fri, 17 Apr 2020 15:07:18 +0900	[thread overview]
Message-ID: <004b01d6147e$73115980$59340c80$@samsung.com> (raw)
In-Reply-To: <ef3cdac4-9967-a225-fb04-4dbb4c7037a9@sandeen.net>

> I've seen 2 issues w/ exfat timestamps - discovered by xfstests
> generic/003
> 
> 1) time granularity is set wrong, so subsecond timestamps change when
>    an inode cycles out of memory and is reread from disk
> 
> 2) the disk format doesn't seem to support subsecond atime, so a similar
>    problem exists there.e
> 
> The last xfstests generic/003 issue is re: change time but exfat doesn't
> really support change times (?) so that'll be a test workaround.
Applied.
Thanks!


      parent reply	other threads:[~2020-04-17  6:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200416010734epcas1p38e25193dcaf42638ee8fd183afe2a112@epcas1p3.samsung.com>
2020-04-16  1:07 ` [PATCH 0/2] exfat: timestamp fixes Eric Sandeen
2020-04-16  1:09   ` [PATCH 1/2] exfat: properly set s_time_gran Eric Sandeen
2020-04-19  3:15     ` Matthew Wilcox
2020-04-20 23:28       ` Namjae Jeon
2020-04-16  1:12   ` [PATCH 2/2] exfat: zero out atime subsecond timestamp Eric Sandeen
2020-04-16  4:11     ` [PATCH 2/2 V2] exfat: truncate atimes to 2s granularity Eric Sandeen
2020-04-18 13:03       ` Namjae Jeon
2020-04-18 13:37         ` Namjae Jeon
2020-04-18 16:04         ` Eric Sandeen
2020-04-18 16:40           ` Eric Sandeen
2020-04-18 17:06             ` Eric Sandeen
2020-04-18 22:55               ` Namjae Jeon
2020-04-18 22:52             ` Namjae Jeon
2020-04-18 22:50           ` Namjae Jeon
2020-04-17  6:07   ` Namjae Jeon [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='004b01d6147e$73115980$59340c80$@samsung.com' \
    --to=namjae.jeon@samsung.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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;
as well as URLs for NNTP newsgroup(s).