Kernel

Now they are at r6. I hope that FreeBSD will have dabian base for their 3.x series soon, which will provide better compatibility and ease the way of users to migrate to FreeBSD.

So he has finally (after about six or more months) imported read-only ResierFS, congratulations, dumbbell, you have made a quite impressive change!

Since 6-ism VFS interface is quite different from 5-ism, so this change is not likely to be merged IMO. Read-write is also not likely to be available soon, but anyway, ReiserFS is a nice FS and supporting it is a good move.

Today another GPL kernel has problem with a 4TB RAID5 array, it thought that it is 2.1TB (on boot) and refuse to initialize it with its native file systems, including ReiserFS. On contrary, FreeBSD 5.4 and 6.0 works smoothly with a GENERIC kernel. Oh well…

在-CURRENT上发表那个patch之后果然有很多热心人帮助测试。有人说在X里面接USB键盘会花，现在还在找原因……

So I finally got a big pointyhat…

This is the point:

if (!_ioctl(fd, FIODGNAME, &fgn))

So this means SUCCEEDED and the return value should be used. However, my recent commit has reverted the logic so that will fail. Seems sshd(1) don’t like this…

Fixed now.

Jeffrey Hsu (a well known FreeBSD and DragonFly networking stack developer) has committed first cut of TCP ABC implementation for DragonFlyBSD. Described in RFC 3465, this is an improvement that can provide better throughput.

Colin is very effective man that has made some changes to the kernel, and so@ has approved this, and 5.4-RELEASE gets its first patchlevel.

I’m happy that this did not forced me to go to the hosting provider :-)

Today, Colin has committed three security fixes that addresses three medium-risk security issues in FreeBSD kernel. That results in p11, p12 and p13 of FreeBSD 5.3-RELEASE, and has been committed to RELENG_5_4 as well so we will get that in the final release build.

Ken Smith has announced the tagging (with a mini heads-up in developers@), and then committed the naming (5.4-RELEASE) to the RELENG_5_4 tree. After that, RELENG_5_4 was tagged as RELENG_5_4_0_RELEASE, which is the last step of the release engineering that is related to the src/tree.

Please note that, this is not the final step of the final release. FreeBSD is very careful about the quality (not only as opposed to the kernel with colorful history of its security record, which is released under GPL and often release from time to time, haha, you know which is that) of a release, therefore, tagging does not mean that “we made it”, that is just a stage. Please be patient to wait for the PGP signed 5.4-RELEASE announcement BEFORE you download isos, even they were found on any sites.

I have enabled PREEMPTION, FULL_PREEMPTION with ULE. Now I get strange result here:

• propagate_priority gets a TD_ON_LOCK(td)
• It tries to panic(), unfortunatelly, ts->ts_lockobj here is NULL
• A fatal trap 12 happens.

It seems that ts->ts_lockobj was touched by sched_lend_prio, for unknown reasons. Maybe there is some lock releases?

调试能力明显下降了，本来早就应该想到的，结果整整花了一个钟头才找到故障点，老了，明明看到堆栈毁了的居然还去相信调试器：（

Finally I caught the kernel panic caused by some strange bugs found in thread scheduling. Investigating the crashdump.