summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_thread.c
diff options
context:
space:
mode:
authormckusick <mckusick@FreeBSD.org>2003-02-25 23:21:08 +0000
committermckusick <mckusick@FreeBSD.org>2003-02-25 23:21:08 +0000
commit259fedfc3c31b8d9e7baaea3ffe4112cea37511a (patch)
treed5f219b74d598030bc288d170776c12d5a1cc4f7 /sys/kern/kern_thread.c
parent8c4aaea3e2b50ba0f23f0712fb2a02c3667c7fdd (diff)
downloadFreeBSD-src-259fedfc3c31b8d9e7baaea3ffe4112cea37511a.zip
FreeBSD-src-259fedfc3c31b8d9e7baaea3ffe4112cea37511a.tar.gz
Change the field used to test whether the superblock has been updated
from the filesystem size field to the filesystem maximum blocksize field. The problem is that older versions of growfs updated only the new size field and not the old size field. This resulted in the old (smaller) size field being copied up to the new size field which caused the filesystem to appear to fsck to be badly trashed. This also adds a sanity check to ensure that the superblock is not being updated when the filesystem is mounted read-only. Obviously such an update should never happen. Reported by: Nate Lawson <nate@root.org> Sponsored by: DARPA & NAI Labs.
Diffstat (limited to 'sys/kern/kern_thread.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud