Date: Tue, 28 Nov 2006 20:04:11 -0800 From: Nate Lawson <nate@root.org> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/i386/i386 local_apic.c src/sys/amd64/amd64 local_apic.c Message-ID: <456D06BB.6010007@root.org> In-Reply-To: <20061129011937.4DEA816A5B0@hub.freebsd.org> References: <20061129011937.4DEA816A5B0@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Sobolev wrote: > sobomax 2006-11-29 01:19:23 UTC > > FreeBSD src repository > > Modified files: (Branch: RELENG_6) > sys/i386/i386 local_apic.c > sys/amd64/amd64 local_apic.c > Log: > Another attempt to MFC changes that prevent any accounting for the disabled > HTT cores. This time make code conditional on !defined(SCHED_ULE), since > SCHED_ULE is generally b0rken due to the fact that it doesn't honour > hlt_cpus_mask when scheduling processes like all other schedulers in the > system do. > > I am not sure if such SCHED_ULE behaviour should be considered as a > security flaw, basically it means that anybody running SCHED_ULE kernel > on HTT system still affected by FreeBSD-SA-05:09.htt. > > Revision Changes Path > 1.17.2.11 +16 -0 src/sys/amd64/amd64/local_apic.c > 1.17.2.11 +16 -0 src/sys/i386/i386/local_apic.c No, since FreeBSD-SA-05:09.htt is not a HTT problem, it's a cache problem that is exploitable on single thread/core systems as well. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?456D06BB.6010007>