Heads up! 4.x developers / testers. A bunch of bug fixes have been
committed, including a big involved one that solves problems related in
the getnewbuf() thread by basically rewriting getnewbuf().
At least a half dozen bug fixes by various authors have been committed in
recent days covering over a dozen files in the VM system. While these
are supposed to be bug fixes, care should be taken when running an
updated -current system.
Please review the commit logs. Here is an overview:
* VFS/BIO fixes
getnewbuf() has been fixed to (A) not recurse 5 levels,
which can run the supervisor stack out when the system has
long VFS call chains, and (B) handle extreme low-memory
situations without deadlocking.
* VM fixes
A read()/mmap()/open() deadlock has been fixed.
DG has upped reserved KVM space to 1G, solving large-memory
and large-maxusers configuration problems. Note: you must
have the latest bootblocks and /boot directory for new kernels
to boot properly.
* NFS fixes
NFS was not properly clearing B_DONE in some cases, leading
to process lockups due to code in biodone() which would not
wakeup the bp if it was already marked B_DONE. biodone()
now (properly) panics if the bp is already marked B_DONE, and
the NFS code now properly clears B_DONE prior to initiating
a new I/O operation.
* CCD fixes
An overflow in CCD that disallowing large stripe sizes
( > 2GB ) has been fixed.
* MFS fixes
An earlier commit that fixes a low-swap/kill problem created
a 'syncing filesystems...giving up' problem. This has been
fixed.
The more trivial bug fixes have been backported to -3.x. The others are
under review.
-Matt
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
