From: Yangtao Li <frank.li@vivo.com>
To: slava@dubeyko.com, glaubitz@physik.fu-berlin.de,
Yangtao Li <frank.li@vivo.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 2/3] hfs: correct superblock flags
Date: Fri, 30 May 2025 02:17:17 -0600 [thread overview]
Message-ID: <20250530081719.2430291-2-frank.li@vivo.com> (raw)
In-Reply-To: <20250530081719.2430291-1-frank.li@vivo.com>
We don't support atime updates of any kind,
because hfs actually does not have atime.
dirCrDat: LongInt; {date and time of creation}
dirMdDat: LongInt; {date and time of last modification}
dirBkDat: LongInt; {date and time of last backup}
filCrDat: LongInt; {date and time of creation}
filMdDat: LongInt; {date and time of last modification}
filBkDat: LongInt; {date and time of last backup}
Signed-off-by: Yangtao Li <frank.li@vivo.com>
---
fs/hfs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/hfs/super.c b/fs/hfs/super.c
index fe09c2093a93..9fab84b157b4 100644
--- a/fs/hfs/super.c
+++ b/fs/hfs/super.c
@@ -331,7 +331,7 @@ static int hfs_fill_super(struct super_block *sb, struct fs_context *fc)
sbi->sb = sb;
sb->s_op = &hfs_super_operations;
sb->s_xattr = hfs_xattr_handlers;
- sb->s_flags |= SB_NODIRATIME;
+ sb->s_flags |= SB_NOATIME;
mutex_init(&sbi->bitmap_lock);
res = hfs_mdb_get(sb);
--
2.48.1
next prev parent reply other threads:[~2025-05-30 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 8:17 [PATCH v3 1/3] hfsplus: fix to update ctime after rename Yangtao Li
2025-05-30 8:17 ` Yangtao Li [this message]
2025-05-30 16:30 ` [PATCH v3 2/3] hfs: correct superblock flags Viacheslav Dubeyko
2025-05-30 8:17 ` [PATCH v3 3/3] hfs: fix to update ctime after rename Yangtao Li
2025-05-30 16:33 ` Viacheslav Dubeyko
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=20250530081719.2430291-2-frank.li@vivo.com \
--to=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.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®