From owner-freebsd-commit  Sat Sep 23 14:13:08 1995
Return-Path: owner-commit
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id OAA01309
          for freebsd-commit-outgoing; Sat, 23 Sep 1995 14:13:08 -0700
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id OAA01292
          for cvs-all-outgoing; Sat, 23 Sep 1995 14:12:59 -0700
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id OAA01282
          for cvs-sys-outgoing; Sat, 23 Sep 1995 14:12:56 -0700
Received: (from dyson@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id OAA01271
          ; Sat, 23 Sep 1995 14:12:48 -0700
Date: Sat, 23 Sep 1995 14:12:48 -0700
From: John Dyson <dyson>
Message-Id: <199509232112.OAA01271@freefall.freebsd.org>
To: CVS-commiters, cvs-sys
Subject: cvs commit: src/sys/kern vfs_bio.c vfs_cluster.c
Sender: owner-commit@FreeBSD.org
Precedence: bulk

dyson       95/09/23 14:12:47

  Modified:    sys/kern  vfs_bio.c vfs_cluster.c
  Log:
  These changes fix a bug in the clustering code that I made worse when adding
  support for EXT2FS.  Note that the Sig-11 problems appear to be caused by
  this, but there is still probably an underlying VM problem that let this
  clustering bug cause vnode objects to appear to be corrupted.
  
  The direct manifestation of this bug would have been severely mis-read
  files.  It is possible that processes would Sig-11 on very damaged
  input files and might explain the mysterious differences in system
  behaviour when phk's malloc is being used.