summaryrefslogtreecommitdiffstats
path: root/sys/dev/pccard/pccard_cis_quirks.c
diff options
context:
space:
mode:
authorrwatson <rwatson@FreeBSD.org>2000-04-19 07:38:20 +0000
committerrwatson <rwatson@FreeBSD.org>2000-04-19 07:38:20 +0000
commit5b36470f2033fd9b5d9ae54ce79ef9909a5dba1b (patch)
tree6f17b83fa35f5dc6ebc20226718cadf028b0c3ae /sys/dev/pccard/pccard_cis_quirks.c
parent4d657494f01bde4f682e703a40361d3f4282999d (diff)
downloadFreeBSD-src-5b36470f2033fd9b5d9ae54ce79ef9909a5dba1b.zip
FreeBSD-src-5b36470f2033fd9b5d9ae54ce79ef9909a5dba1b.tar.gz
o Cause attribute data writes to use IO_SYNC since this improves the
chances of consistency with other file/directory meta-data in a write. In the current set of extended attribute applications, this does not hurt much. This should be discussed again later when it comes time to optimize performance of attributes. o Include an inode generation number in the per-attribute header information. This allows consistency verification to catch when a crash occurs, or an inode is recycled while attributes are not properly configured. For now, an irritating error message is displayed when an inconsistency occurs. At some point, may introduce an ``extattrctl check ...'' which catches these before attributes are enabled. Not today. If you get this message, it means you somehow managed to get your attribute backing file out of synch with the file system. When this occurs, attribute not found is returned (== undefined). Writes will overwrite the value there correcting the problem. Might want to think about introducing a new errno or two to handle this kind of situation. Discussed with: kris
Diffstat (limited to 'sys/dev/pccard/pccard_cis_quirks.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud