From: 郑浩然 <zhenghaoran@buaa.edu.cn>
To: torvalds@linux-foundation.org, viro@zeniv.linux.org.uk,
brauner@kernel.org, mjguzik@gmail.com, willy@infradead.org,
linux@treblig.org, djwong@kernel.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: 21371365@buaa.edu.cn, baijiaju1990@gmail.com, zhenghaoran@buaa.edu.cn
Subject: Re: [RFC] metadata updates vs. fetches (was Re: [PATCH v4] fs: Fix data race in inode_set_ctime_to_ts)
Date: Tue, 26 Nov 2024 14:44:52 +0800 (GMT+08:00) [thread overview]
Message-ID: <7ed332aa.d50.193673739e3.Coremail.zhenghaoran@buaa.edu.cn> (raw)
Sorry for the previous email in html format, here is the resent
email in plain ASCII text format.
Thanks for your replies. During further testing, I found that the
same problem also occurred with `mtime` and `atime`. I already
understand that this bug may have limited impact, but should I do
something else to deal with this series of timestamp-related issues?
The new call stack is as follows
============DATA_RACE============
btrfs_write_check+0x841/0x13f0 [btrfs]
btrfs_buffered_write+0x6a9/0x2c90 [btrfs]
btrfs_do_write_iter+0x4b7/0x16d0 [btrfs]
btrfs_file_write_iter+0x41/0x60 [btrfs]
aio_write+0x445/0x600
io_submit_one+0xd68/0x1cf0
__se_sys_io_submit+0xc4/0x270
do_syscall_64+0xc9/0x1a0
entry_SYSCALL_64_after_hwframe+0x77/0x7f
0x0
============OTHER_INFO============
btrfs_delayed_update_inode+0x1e24/0x80e0 [btrfs]
btrfs_update_inode+0x478/0xbc0 [btrfs]
btrfs_finish_one_ordered+0x24d6/0x36a0 [btrfs]
btrfs_finish_ordered_io+0x37/0x60 [btrfs]
finish_ordered_fn+0x3e/0x50 [btrfs]
btrfs_work_helper+0x9c9/0x27a0 [btrfs]
process_scheduled_works+0x716/0xf10
worker_thread+0xb6a/0x1190
kthread+0x292/0x330
ret_from_fork+0x4d/0x80
ret_from_fork_asm+0x1a/0x30
=================================
next reply other threads:[~2024-11-26 6:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 6:44 郑浩然 [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-23 14:01 [PATCH v3] fs: Fix data race in inode_set_ctime_to_ts Jeff Layton
2024-11-24 9:42 ` [PATCH v4] " Hao-ran Zheng
2024-11-24 17:44 ` Darrick J. Wong
2024-11-24 17:56 ` Mateusz Guzik
2024-11-24 21:50 ` [RFC] metadata updates vs. fetches (was Re: [PATCH v4] fs: Fix data race in inode_set_ctime_to_ts) Al Viro
2024-11-24 22:10 ` Linus Torvalds
2024-11-24 22:24 ` Al Viro
2024-11-24 22:34 ` Matthew Wilcox
2024-11-24 22:43 ` Linus Torvalds
2024-11-24 23:53 ` Matthew Wilcox
2024-11-25 0:53 ` Linus Torvalds
2024-11-25 1:02 ` Linus Torvalds
2024-11-25 1:15 ` Matthew Wilcox
2024-11-25 1:26 ` Linus Torvalds
2024-11-24 22:40 ` Linus Torvalds
2024-11-24 23:05 ` Mateusz Guzik
2024-11-24 23:19 ` Mateusz Guzik
2024-11-24 23:41 ` Al Viro
2024-11-24 23:38 ` Al Viro
2024-11-25 12:20 ` Christian Brauner
2024-11-24 22:10 ` Dr. David Alan Gilbert
2024-11-24 22:19 ` Matthew Wilcox
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=7ed332aa.d50.193673739e3.Coremail.zhenghaoran@buaa.edu.cn \
--to=zhenghaoran@buaa.edu.cn \
--cc=21371365@buaa.edu.cn \
--cc=baijiaju1990@gmail.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mjguzik@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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®