From owner-cvs-sys Fri Sep 19 04:18:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA04426 for cvs-sys-outgoing; Fri, 19 Sep 1997 04:18:00 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA04374; Fri, 19 Sep 1997 04:17:19 -0700 (PDT) From: Poul-Henning Kamp Received: (from phk@localhost) by freefall.freebsd.org (8.8.6/8.8.5) id EAA00449; Fri, 19 Sep 1997 04:13:19 -0700 (PDT) Date: Fri, 19 Sep 1997 04:13:19 -0700 (PDT) Message-Id: <199709191113.EAA00449@freefall.freebsd.org> To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-sys@FreeBSD.ORG Subject: cvs commit: src/sys/ufs/ffs ffs_alloc.c Sender: owner-cvs-sys@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk phk 1997/09/19 04:13:19 PDT Modified files: sys/ufs/ffs ffs_alloc.c Log: [Regarding the previous patch] This is completely wrong. 1. ffs_alloc() actually allowed writing one block less one frag (normally 7 frags or 7/8 blocks) beyond the limit. 2. freebufspace() gives the free space in frags, but `size' is in bytes, so the change results in approximately `size' fragments too many being reserved. 3. ffs_realloccg() has the same bug but wasn't changed. PR: 3398 Submitted by: bde Eyeballed by: phk Revision Changes Path 1.37 +5 -3 src/sys/ufs/ffs/ffs_alloc.c