summaryrefslogtreecommitdiffstats
path: root/fs/xfs/xfs_attr.h
diff options
context:
space:
mode:
authorEric Sandeen <sandeen@sandeen.net>2016-04-06 07:57:18 +1000
committerDave Chinner <david@fromorbit.com>2016-04-06 07:57:18 +1000
commit2a6fba6d2311151598abaa1e7c9abd5f8d024a43 (patch)
tree6ff4d9edda91b530deff6386dd796e6e91e6e121 /fs/xfs/xfs_attr.h
parentf55532a0c0b8bb6148f4e07853b876ef73bc69ca (diff)
downloadtalos-obmc-linux-2a6fba6d2311151598abaa1e7c9abd5f8d024a43.tar.gz
talos-obmc-linux-2a6fba6d2311151598abaa1e7c9abd5f8d024a43.zip
xfs: only return -errno or success from attr ->put_listent
Today, the put_listent formatters return either 1 or 0; if they return 1, some callers treat this as an error and return it up the stack, despite "1" not being a valid (negative) error code. The intent seems to be that if the input buffer is full, we set seen_enough or set count = -1, and return 1; but some callers check the return before checking the seen_enough or count fields of the context. Fix this by only returning non-zero for actual errors encountered, and rely on the caller to first check the return value, then check the values in the context to decide what to do. Signed-off-by: Eric Sandeen <sandeen@redhat.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'fs/xfs/xfs_attr.h')
-rw-r--r--fs/xfs/xfs_attr.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/xfs/xfs_attr.h b/fs/xfs/xfs_attr.h
index dd4824589470..234331227c0c 100644
--- a/fs/xfs/xfs_attr.h
+++ b/fs/xfs/xfs_attr.h
@@ -112,6 +112,7 @@ typedef struct attrlist_cursor_kern {
*========================================================================*/
+/* Return 0 on success, or -errno; other state communicated via *context */
typedef int (*put_listent_func_t)(struct xfs_attr_list_context *, int,
unsigned char *, int, int, unsigned char *);
OpenPOWER on IntegriCloud