Re: [patch] let CONFIG_SECCOMP default to n

On Wed, 12 Jul 2006, Chuck Ebbert wrote:
>
> We can just fold the TSC disable stuff into the new thread_flags test
> at context-switch time:

I really think that this should be cleaned up to _not_ confuse the issue 
of TSC with any "secure computing" issue.

The two have nothing to do with each other from a technical standpoint. 

Just make the flag be called "TIF_NOTSC", and then any random usage 
(whether it be seccomp or anything else) can just set that flag, the same 
way ioperm() sets TIF_IO_BITMAP.

Much cleaner. 

There's no point in mixing up an implementation detail like SECCOMP with a 
feature like this.

			Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch] let CONFIG_SECCOMP default to n
    • From: [email protected]

• References:
  • Re: [patch] let CONFIG_SECCOMP default to n
    • From: Chuck Ebbert <[email protected]>

• Prev by Date: Re: [PATCH] Use uname not sysctl to get the kernel revision
• Next by Date: Re: [PATCH] Use uname not sysctl to get the kernel revision
• Previous by thread: Re: [patch] let CONFIG_SECCOMP default to n
• Next by thread: Re: [patch] let CONFIG_SECCOMP default to n
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]