| Patrick Williams | d8c66bc | 2016-06-20 12:57:21 -0500 | [diff] [blame] | 1 | From a24cf102967a4966bfabe36c3542fb65f35bf539 Mon Sep 17 00:00:00 2001 |
| 2 | From: Peter Seebach <peter.seebach@windriver.com> |
| 3 | Date: Wed, 23 Mar 2016 11:55:25 -0500 |
| 4 | Subject: actually handle remove_xattr correctly |
| 5 | |
| 6 | The path is required but wasn't being extracted from the client's message, |
| 7 | resulting in xattr removal never working. This does not fully address some |
| 8 | deeper problems with the xattr implementation, but at least the common |
| 9 | removal case works. |
| 10 | |
| 11 | Upstream-Status: Backport |
| 12 | |
| 13 | Index: pseudo-1.7.5/ChangeLog.txt |
| 14 | =================================================================== |
| 15 | --- pseudo-1.7.5.orig/ChangeLog.txt |
| 16 | +++ pseudo-1.7.5/ChangeLog.txt |
| 17 | @@ -1,3 +1,7 @@ |
| 18 | +2016-03-22: |
| 19 | + * (seebs) extract path from message for remove_xattr so it |
| 20 | + actually works. |
| 21 | + |
| 22 | 2016-02-09: |
| 23 | * (seebs) 1.7.5 release |
| 24 | |
| 25 | Index: pseudo-1.7.5/pseudo.c |
| 26 | =================================================================== |
| 27 | --- pseudo-1.7.5.orig/pseudo.c |
| 28 | +++ pseudo-1.7.5/pseudo.c |
| 29 | @@ -543,6 +543,7 @@ pseudo_op(pseudo_msg_t *msg, const char |
| 30 | case OP_GET_XATTR: |
| 31 | case OP_LIST_XATTR: |
| 32 | case OP_REPLACE_XATTR: |
| 33 | + case OP_REMOVE_XATTR: |
| 34 | case OP_SET_XATTR: |
| 35 | /* In a rename there are two paths, null separated in msg->path */ |
| 36 | initial_len = strlen(msg->path); |