Re: [PATCH for 2.6.18rc2] [1/7] i386/x86-64: Don't randomize stack top when no randomization personality is set

> -	if (current->flags & PF_RANDOMIZE) {
> +	if ((current->flags & PF_RANDOMIZE) &&
> +		!(current->personality & ADDR_NO_RANDOMIZE)) {

these should be exclusive anyway, isn't the right solution to clear
PF_RANDOMIZE on ADDR_NO_RANDOMIZE personality ?

-
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/

---

• References:
  • [PATCH for 2.6.18rc2] [1/7] i386/x86-64: Don't randomize stack top when no randomization personality is set
    • From: "Andi Kleen" <[email protected]>

• Prev by Date: [PATCH] Sane return value for ecryptfs_commit_write()
• Next by Date: Re: NFS errors
• Previous by thread: [PATCH for 2.6.18rc2] [1/7] i386/x86-64: Don't randomize stack top when no randomization personality is set
• Next by thread: [PATCH for 2.6.18rc2] [7/7] i386: Do backtrace fallback too
• 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]