共 215 篇文章。
Yes, it is long awaited and Kirk recently announced that his new book (written with George Neville-Neil) about the design and implementation of the FreeBSD 5.2 Operating System has been finished, and will be ready for sale in early August 2004 (ISBN 0-201-70245-2, Addison-Wesley).
Olivier Houchard (cognet) has just committed several files to support the ARM architecture. I have already slipped tags for this change.
From the commit log:
Close an interrupt race between vm_page_lookup() and (typically) a vm_page_sleep_busy() check by using the correct spl protection. An interrupt can occur inbetween the two operations and unbusy/free the page in question, causing the busy check to fail and for the code to fall through and then operate on a page that may have been freed and possibly even reused. Also note that vm_page_grab() had the same issue between the lookup, busy check, and vm_page_busy() call.
I am thinking of the possiblity of backporting / porting several DragonFly and NetBSD, even OpenBSD’s features, to FreeBSD, to increase its performance, stablity, and the code readablity.
By Google’ing the web I got a 1.1.5.1-RELEASE tarball. FreeBSD 1.x was based on Net/2 and the USL lawsuit has caused FreeBSD project to re-start from 4.4BSD-Lite2, and 1.1.5.1 was the last 1.x RELEASE permitted to be released.
Shortly after OpenBSD’s 3.5 splash web, Matthew Dillon has released a thrid “known stable” iso for DragonFlyBSD. It can be obtained from ftp://ftp.dragonflybsd.org/iso-images/dfly-20040502.iso.gz.
This snapshot included many new features, yet stable:
What’are LORs? To quote Robert Watson:
“These warnings are generated by Witness, a run-time lock diagnostic system found in FreeBSD 5-CURRENT kernels (but removed in releases). You can read more about Witness in the WITNESS(4) man page, which talks about its capabilities. Among other things, Witness performs run-time lock order verification using a combination of hard coded lock orders, and run-time detected lock orders, and generates console warnings when lock orders are violated. The intent of this is to detect the potential for deadlocks due to lock order violations; it’s worth observing that Witness is actually slightly conservative, and so it’s possible to get false positives. In the event that Witness is accurately reporting a lock order problem, it’s basically saying “If you were unlucky, a deadlock would have happened here”. There are a couple of “well known” false positives, which we need to do a better job of documenting to prevent spurious reports. The non-well-known ones typically correspond to bugs in newly added locking, as lock order reversals usually get fixed pretty quickly because Witness is busy generating warnings :-).”
Mike Silberack has posted a patch related to illegal TCP RST attacks.
Now we have RELENG_4_10 branch :-) There are a lot of -CURRENT improvements has been MFC’ed, however, the most important part of -CURRENT, say, KSE and SMPng, will never be MFC’ed because of the architecture change introduced by this.
I’m going on to track down the Pentium 4 HTT issue of FreeBSD. Currently I have setup a tinderbox (hengdm’s workstation because he is not here :-P and it’s the only box which supports HTT) and compiled a SMP kernel on it.