summaryrefslogtreecommitdiffstats
path: root/fs/xfs/xfs_extent_busy.h
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@redhat.com>2012-09-26 11:36:16 -0400
committerJ. Bruce Fields <bfields@redhat.com>2012-10-01 17:40:04 -0400
commit0d22f68f02c10d5d10ec5712917e5828b001a822 (patch)
tree7b0d005f8bffe4623c1df2d65a14d321598c70c9 /fs/xfs/xfs_extent_busy.h
parent6a3b15634279aa6740f9b829d25db32024b2ca7c (diff)
downloadblackbird-op-linux-0d22f68f02c10d5d10ec5712917e5828b001a822.tar.gz
blackbird-op-linux-0d22f68f02c10d5d10ec5712917e5828b001a822.zip
nfsd4: don't allow reclaims of expired clients
When a confirmed client expires, we normally also need to expire any stable storage record which would allow that client to reclaim state on the next boot. We forgot to do this in some cases. (For example, in destroy_clientid, and in the cases in exchange_id and create_session that destroy and existing confirmed client.) But in most other cases, there's really no harm to calling nfsd4_client_record_remove(), because it is a no-op in the case the client doesn't have an existing The single exception is destroying a client on shutdown, when we want to keep the stable storage records so we can recognize which clients will be allowed to reclaim when we come back up. Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/xfs/xfs_extent_busy.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud