---

yaml
---
r: 274647
b: refs/heads/master
c: ed3ee9f
h: refs/heads/master
i:
  274645: d3d745c
  274643: 9ef2d88
  274639: 7a43423
v: v3

[refs]

@@ -1,2 +1,2 @@
 ---
-refs/heads/master: e70bea5fe0e3d6355fd95674eaff5aa5a32f0564
+refs/heads/master: ed3ee9f44ba55eb6acfbfc8caa881e0253710d2a

trunk/fs/btrfs/xattr.c

@@ -127,6 +127,17 @@ static int do_setxattr(struct btrfs_trans_handle *trans,
 again:
 	ret = btrfs_insert_xattr_item(trans, root, path, btrfs_ino(inode),
 				      name, name_len, value, size);
+	/*
+	 * If we're setting an xattr to a new value but the new value is say
+	 * exactly BTRFS_MAX_XATTR_SIZE, we could end up with EOVERFLOW getting
+	 * back from split_leaf.  This is because it thinks we'll be extending
+	 * the existing item size, but we're asking for enough space to add the
+	 * item itself.  So if we get EOVERFLOW just set ret to EEXIST and let
+	 * the rest of the function figure it out.
+	 */
+	if (ret == -EOVERFLOW)
+		ret = -EEXIST;
+
 	if (ret == -EEXIST) {
 		if (flags & XATTR_CREATE)
 			goto out;