On Fri, 15 Aug 2008 14:50:01 EDT, Kenneth Goldman said:Well, on a dual/quad core/socket/whatever system, a failing processor can be downed and the system keep going. On a NUMA box, you can yank a node with a bad memory controller after you take it down. Similarly for a disk controller if you have more than one, and the failed one isn't critical for system operation. And the TPM chip is more like a USB controller, in that there's a *high* degree of probability that the system will still be able to run even if it fails or goes insane (consider that on my laptop, the TPM driver was broken for a while, and I was still ableto work). So you need to write code to do things like detect TPM downage or insanity, decide what to do on the kernel level, what to reflect up to any security modules running in userspace, etc....
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Andrew Morton | Re: 2.6.23-rc6-mm1 |
| Luciano Rocha | usb hdd problems with 2.6.27.2 |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Andrew Morton | Re: [BUG] New Kernel Bugs |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH take 2] pkt_sched: Protect gen estimators under est_lock. |
