summaryrefslogtreecommitdiffstats
path: root/sys/kern/vfs_extattr.c
diff options
context:
space:
mode:
authoradrian <adrian@FreeBSD.org>2001-03-31 15:19:58 +0000
committeradrian <adrian@FreeBSD.org>2001-03-31 15:19:58 +0000
commit1d52622861ade01fba488110e63ed8ba868cfcdf (patch)
tree94a7d2d92d425831f0e78018eb656e0bea7daa76 /sys/kern/vfs_extattr.c
parent8b4d22a1bbe92cf8b73395b1464db7c8d8055840 (diff)
downloadFreeBSD-src-1d52622861ade01fba488110e63ed8ba868cfcdf.zip
FreeBSD-src-1d52622861ade01fba488110e63ed8ba868cfcdf.tar.gz
Quoting from the email thrown around between kirk, bde and iedowse@..
<QUOTE> Overflow of cg_niblk causes spurious "SUMMARY INFORMATION BAD" warnings prompts in fsck_ffs. cg_niblk has type int16_t, but it is (ab)used to hold the number of inodes per group (it has nothing to do with the number of inode blocks in the cg as claimed in ffs/fs.h), and there can be lots of inodes per group. E.g., newfs -i 8192 -b 16384 -f 16384 -c 255 ... gives 0xA900 inodes/group. Assignment of this to cg_niblk gives -0x5700. This is mostly harmless (ufs/ffs doesn't use cg_niblk, and bug-for-bug compatible overflow occurs in newfs), but in fsck_ffs/pass5.c, negative values of cg_niblk limit cg_irotor to 0 and the summary info appears to be bad. </QUOTE> Submitted by: Bruce Evans <bde@zeta.org.au> Obtained from: Kirk McKusick <mckusick@mckusick.com>
Diffstat (limited to 'sys/kern/vfs_extattr.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud