cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Eiichi Tsukata <devel@etsukata.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v1 2/4] ext4: fix race between llseek SEEK_END and write
Date: Wed, 21 Nov 2018 11:43:58 +0900	[thread overview]
Message-ID: <20181121024400.4346-3-devel@etsukata.com> (raw)
In-Reply-To: <20181121024400.4346-1-devel@etsukata.com>

Implement individual lock for SEEK_END for ext4 which directly calls
generic_file_llseek_size().

Signed-off-by: Eiichi Tsukata <devel@etsukata.com>
---
 fs/ext4/file.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/fs/ext4/file.c b/fs/ext4/file.c
index 69d65d49837b..6479f3066043 100644
--- a/fs/ext4/file.c
+++ b/fs/ext4/file.c
@@ -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);
-- 
2.19.1



  parent reply	other threads:[~2018-11-21  2:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21  2:43 [Cluster-devel] [PATCH v1 0/4] fs: fix race between llseek SEEK_END and write Eiichi Tsukata
2018-11-21  2:43 ` [Cluster-devel] [PATCH v1 1/4] vfs: " Eiichi Tsukata
2018-11-21  2:43 ` Eiichi Tsukata [this message]
2018-11-21  2:43 ` [Cluster-devel] [PATCH v1 3/4] f2fs: " Eiichi Tsukata
2018-11-21  9:23   ` Christoph Hellwig
2018-11-22  5:42     ` Eiichi Tsukata
2018-11-21  2:44 ` [Cluster-devel] [PATCH v1 4/4] overlayfs: " Eiichi Tsukata
2018-11-21  4:54 ` [Cluster-devel] [PATCH v1 0/4] fs: " Al Viro
2018-11-22  5:40   ` Eiichi Tsukata
2018-11-22  7:06     ` Al Viro
2018-11-26  2:54       ` Eiichi Tsukata

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=20181121024400.4346-3-devel@etsukata.com \
    --to=devel@etsukata.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;
as well as URLs for NNTP newsgroup(s).