From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 207717] New: reiserfs: data race on inode->i_size in reiserfs_write_full_page()
Date: Wed, 13 May 2020 03:28:02 +0000 [thread overview]
Message-ID: <bug-207717-695@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=207717
Bug ID: 207717
Summary: reiserfs: data race on inode->i_size in
reiserfs_write_full_page()
Product: File System
Version: 2.5
Kernel Version: 5.4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ReiserFS
Assignee: reiserfs-devel@vger.kernel.org
Reporter: baijiaju1990@gmail.com
Regression: No
The functions reiserfs_write_full_page() and reiserfs_write_end() are
concurrently executed at runtime in the following call contexts:
Thread 1:
reiserfs_writepage()
reiserfs_write_full_page()
Thread 2:
reiserfs_write_end()
In reiserfs_write_full_page():
unsigned long end_index = inode->i_size >> PAGE_SHIFT;
In reiserfs_write_end():
inode->i_size = pos + copied;
Thus, a data race on inode->i_size occurs.
This data race was found and actually reproduced by our concurrency fuzzer.
I am not sure whether this data race is harmful and how to fix this data race
properly, so I want to listen to your opinions, thanks :)
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-05-13 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 3:28 bugzilla-daemon [this message]
2020-05-13 3:28 ` [Bug 207717] reiserfs: data race on inode->i_size in reiserfs_write_full_page() bugzilla-daemon
2020-05-13 3:31 ` bugzilla-daemon
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=bug-207717-695@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=reiserfs-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.