Maverick pull request for cs-limit nx-emulation refresh

Chase Douglas chase.douglas at
Tue May 25 22:32:35 UTC 2010

On Tue, 2010-05-25 at 15:19 -0700, Kees Cook wrote:
> The following changes since commit 931fecb7a2d93bd931cf07bb2367bb545a3d557f:
>   Leann Ogasawara (1):
>         UBUNTU: Ubuntu-2.6.34-4.11
> are available in the git repository at:
>   git:// master
> Kees Cook (6):
>       Revert "UBUNTU: SAUCE: x86: brk away from exec rand area"
>       Revert "UBUNTU: SAUCE: [um] Don't use nx_enabled under UML"
>       Revert "UBUNTU: SAUCE: [x86] implement cs-limit nx-emulation for ia32"
>       UBUNTU: SAUCE: x86: implement cs-limit nx-emulation for ia32
>       UBUNTU: SAUCE: x86: more tightly confine cs-limit nx-emulation to ia32 only
>       UBUNTU: SAUCE: x86: brk away from exec rand area
> Loïc Minier (1):
>       UBUNTU: SAUCE: [um] Don't use nx_enabled under UML

I'm just curious, what's the process for upstreaming security patches
like these? Are they sauce patches at first while we work with upstream
to get them merged there?

-- Chase

More information about the kernel-team mailing list