Thread (11 messages) 11 messages, 4 authors, 2017-10-02

Re: [PATCH v2 3/4] ext4: Add iomap support for inline data

From: Theodore Ts'o <tytso@mit.edu>
Date: 2017-09-28 17:57:55
Also in: linux-fsdevel, linux-xfs

On Thu, Sep 14, 2017 at 11:50:46AM +0200, Andreas Gruenbacher wrote:
+int ext4_inline_data_iomap(struct inode *inode, struct iomap *iomap)
+{
+	__u64 addr;
+	int error = -EAGAIN;
+	struct ext4_iloc iloc;
+
+	down_read(&EXT4_I(inode)->xattr_sem);
+	if (!ext4_has_inline_data(inode))
+		goto out;
	....
+out:
+	up_read(&EXT4_I(inode)->xattr_sem);
+	return error;
+}

If we race with the inline data flag getting cleared,
ext4_iomap_begin() will return with -EAGAIN.  As near as I can tell,
this will get reflected all the way up to userspace, instead of having
the retry happen in the kernel.  Is this intentional?

It looks like a user visible change, no?

						- Ted
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help