@@ -477,6 +477,16 @@ loff_t ext4_llseek(struct file *file, loff_t offset, int whence)
default:
return generic_file_llseek_size(file, offset, whence,
maxbytes, i_size_read(inode));
+ case SEEK_END:
+ /*
+ * protects against inode size race with write so that llseek
+ * doesn't see inode size being updated in generic_perform_write
+ */
+ inode_lock_shared(inode);
+ offset = generic_file_llseek_size(file, offset, whence,
+ maxbytes, i_size_read(inode));
+ inode_unlock_shared(inode);
+ return offset;
case SEEK_HOLE:
inode_lock_shared(inode);
offset = iomap_seek_hole(inode, offset, &ext4_iomap_ops);
The commit ef3d0fd27e90 ("vfs: do (nearly) lockless generic_file_llseek") removed almost all locks in llseek() including SEEK_END. It based on the idea that write() updates size atomically. But in fact, write() can be divided into two or more parts in generic_perform_write() when pos straddles over the PAGE_SIZE, which results in updating size multiple times in one write(). It means that llseek() can see the size being updated during write(). This race changes behavior of some applications. 'tail' is one of those applications. It reads range [pos, pos_end] where pos_end is obtained via llseek() SEEK_END. Sometimes, a read line could be broken. reproducer: $ while true; do echo 123456 >> out; done $ while true; do tail out | grep -v 123456 ; done example output(take 30 secs): 12345 1 1234 1 12 1234 Signed-off-by: Eiichi Tsukata <devel@etsukata.com> --- fs/ext4/file.c | 10 ++++++++++ 1 file changed, 10 insertions(+)