blob: 64471a3ddb04d3d2dfea92c007799bcc92be101d [file] [log] [blame]
Dave Chinner0b61f8a2018-06-05 19:42:14 -07001// SPDX-License-Identifier: GPL-2.0
Linus Torvalds1da177e2005-04-16 15:20:36 -07002/*
Nathan Scott7b718762005-11-02 14:58:39 +11003 * Copyright (c) 2005 Silicon Graphics, Inc.
4 * All Rights Reserved.
Linus Torvalds1da177e2005-04-16 15:20:36 -07005 */
6#ifndef __XFS_EXPORT_H__
7#define __XFS_EXPORT_H__
8
9/*
10 * Common defines for code related to exporting XFS filesystems over NFS.
11 *
12 * The NFS fileid goes out on the wire as an array of
13 * 32bit unsigned ints in host order. There are 5 possible
14 * formats.
15 *
16 * (1) fileid_type=0x00
17 * (no fileid data; handled by the generic code)
18 *
19 * (2) fileid_type=0x01
20 * inode-num
21 * generation
22 *
23 * (3) fileid_type=0x02
24 * inode-num
25 * generation
26 * parent-inode-num
27 * parent-generation
28 *
29 * (4) fileid_type=0x81
30 * inode-num-lo32
31 * inode-num-hi32
32 * generation
33 *
34 * (5) fileid_type=0x82
35 * inode-num-lo32
36 * inode-num-hi32
37 * generation
38 * parent-inode-num-lo32
39 * parent-inode-num-hi32
40 * parent-generation
41 *
42 * Note, the NFS filehandle also includes an fsid portion which
43 * may have an inode number in it. That number is hardcoded to
44 * 32bits and there is no way for XFS to intercept it. In
Nathan Scottc41564b2006-03-29 08:55:14 +100045 * practice this means when exporting an XFS filesystem with 64bit
Linus Torvalds1da177e2005-04-16 15:20:36 -070046 * inodes you should either export the mountpoint (rather than
47 * a subdirectory) or use the "fsid" export option.
48 */
49
Christoph Hellwigc38344f2007-10-21 16:42:11 -070050struct xfs_fid64 {
51 u64 ino;
52 u32 gen;
53 u64 parent_ino;
54 u32 parent_gen;
55} __attribute__((packed));
56
Linus Torvalds1da177e2005-04-16 15:20:36 -070057/* This flag goes on the wire. Don't play with it. */
58#define XFS_FILEID_TYPE_64FLAG 0x80 /* NFS fileid has 64bit inodes */
59
Linus Torvalds1da177e2005-04-16 15:20:36 -070060#endif /* __XFS_EXPORT_H__ */