Kernel

The following change is considered as a new errata candadite from my view:

peter 2005-04-18 21:36:17 UTC FreeBSD src repository

Modified files: (Branch: RELENG_5_4)
sys/i386/i386 genassym.c vm86bios.s
sys/i386/include pcb.h
Log:
MFC: stop i386_vm86() from either panicing or trashing random pages.

This can improve stability, however we can not easily prove that it is producable :-) So I have turned that to re@.

To quote him:

So I finally tried DragonFly on one of our test servers (not my desktop :-). It seems that DragonFly still have some issues with the SATA devices. I am trying to fix it, maybe by porting some good FreeBSD ATAng code.

DragonFly has gave us some good examples that how a user-friendly operating system should, and some different way on designing a MP-capable architecture. Thanks, Matt!

As title. We *need* to struggle to make the upcoming 6.0-RELEASE a good release . I hope we can show the great improvements taken place in 6-CURRENT and hopefully we can cut 6-STABLE this June.

Highlights on recent 6-CURRENT that was not merged (and may never be merged):

• MPSAFE VFS
• Integrated VFS hashing (generallized, traditionally it’s different on ufs, msdosfs, etc)
• 64bit-ize of several utilities, to ensure better usage of large storage.

They did it again!

CAN-2005-0176
CAN-2005-0177
CAN-2005-0178
CAN-2005-0449

Before patching your already fragile kernel, consider other true Open Source operating systems, like FreeBSD and DragonFlyBSD!

1. We should not caclucate the superblock summary, since it can at most lag 30 seconds’ change, and doing the caclucate is painful delay. What we should do is to transfer the responsibility to background fsck
2. newfs(8) should warn about the snapshot is actually unable to create, in case fssize is greater than maxfilesize.

The patch for 1) is available at http://people.freebsd.org/~delphij/ffs/patch-sbsummary. I will work on 2) shortly, as it’s quite simpler than 1).

好事多磨：

初一：修正了一组SCSI配置问题，MFC掉的那个CAM改进也加入了内核。发现有4台机器硬件存在不同的毛病。
初二：深夜发现一些机器panic，连夜进一步加入新近MFC的UFS2错误修正。
初三：正式部署新的kernel，看上去运转良好。
初四：软件现在已经足够稳定了，但是居然有一台机器SCSI卡出了问题，已经通知厂商取备机……

Every quarter we got the same news: Linux did it again!

Yes, they DID it again. Many sites became victim during the last scan of awstats vulnerability, the most famous ones are www.phpbb.com, and moto.debian.org.tw, etc. You can Google the cracker organization and find more.

Why Linux is again and again vulnerable to these hack attempts? Why other systems doesn’t have such serious security issues even when an exploit is published? The answer is apparant: Linux did worst ever, among all Operating Systems, even when you include Windows. Imagine, a kernel which can permit normal users to gain root privilege.

It seems that if one host is fsck’ing and the other is trying to boot, then the controller will halt. I’m so tired and sick about this!

于是他们又来了。

如果你正在用Linux kernel 2.2.x，2.4.x(从开始到2.4.29-pre3)，2.6.x(从开始到2.6.10)，那么你就有事干了。通过合理地注入代码，任何人都可以拿到root，因为kmem_cache_alloc()的执行过程被打断，则VMA的红黑树可能会在不希望的地方插入一个节点，并进而通过LDT调用门获取CPL0特权。