summaryrefslogtreecommitdiffstats
path: root/support/export/rmtab.c
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2010-05-05 15:41:07 -0400
committerSteve Dickson <steved@redhat.com>2010-05-05 15:42:36 -0400
commit6299a310d77e6495efdf7c50491f0b055fee2cfe (patch)
tree636a10692ff37c4d7fb65f59d4be8a9c91724409 /support/export/rmtab.c
parent6ff1fd42db18c657fbc5f81169a566b41d53e731 (diff)
downloadnfs-utils-6299a310d77e6495efdf7c50491f0b055fee2cfe.tar.gz
nfs-utils-6299a310d77e6495efdf7c50491f0b055fee2cfe.tar.xz
nfs-utils-6299a310d77e6495efdf7c50491f0b055fee2cfe.zip
mountd/exportfs: Make m_addrlist field a nfs_sockaddr
To store non-AF_INET addresses in the nfs_client structure, we need to use more than in_addr for the m_addrlist field. Make m_addrlist larger, then add a few helper functions to handle type casting and array indexing cleanly. We could treat the nfs_client address list as if all the addresses in the list were the same family. This might work for MCL_SUBNETWORK type nfs_clients. However, during the transition to IPv6, most hosts will have at least one IPv4 and one IPv6 address. For MCL_FQDN, I think we need to have the ability to store addresses from both families in one nfs_client. Additionally, IPv6 scope IDs are not part of struct sin6_addr. To support link-local IPv6 addresses and the like, a scope ID must be stored. Thus, each slot in the address list needs to be capable of storing an entire socket address, and not simply the network address part. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Steve Dickson <steved@redhat.com>
Diffstat (limited to 'support/export/rmtab.c')
0 files changed, 0 insertions, 0 deletions