# # NetLabel configuration # config NETLABEL bool "NetLabel subsystem support" depends on SECURITY select CRC_CCITT if IPV6 default n ---help--- NetLabel provides support for explicit network packet labeling protocols such as CIPSO and RIPSO. For more information see Documentation/netlabel as well as the NetLabel SourceForge project for configuration tools and additional documentation. * http://netlabel.sf.net If you are unsure, say N. /git.distanz.ch/cgit.cgi/linux/net-next.git' title='net-next.git Git repository'/>
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2017-01-25 07:49:35 -0800
committerDarrick J. Wong <darrick.wong@oracle.com>2017-01-25 07:49:35 -0800
commit76d771b4cbe33c581bd6ca2710c120be51172440 (patch)
tree1fa79ad971f2dc9502d80a9bdeacbf88a4d2c732
parent4dfa2b84118fd6c95202ae87e62adf5000ccd4d0 (diff)
xfs: use per-AG reservations for the finobt
Currently we try to rely on the global reserved block pool for block allocations for the free inode btree, but I have customer reports (fairly complex workload, need to find an easier reproducer) where that is not enough as the AG where we free an inode that requires a new finobt block is entirely full. This causes us to cancel a dirty transaction and thus a file system shutdown. I think the right way to guard against this is to treat the finot the same way as the refcount btree and have a per-AG reservations for the possible worst case size of it, and the patch below implements that. Note that this could increase mount times with large finobt trees. In an ideal world we would have added a field for the number of finobt fields to the AGI, similar to what we did for the refcount blocks. We should do add it next time we rev the AGI or AGF format by adding new fields. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>