Re: [PATCH 3.5 0/2] seccomp and vsyscall fixes

[Greg KH]

On Thu, Sep 27, 2012 at 12:40:10PM -0700, Andy Lutomirski wrote:
> [cc James Morris]
> 
> This has been pending since the 3.6 merge window.  Patch 2/2 barely
> matters because it's almost impossible to detect its effect -- it's
> more about future proofing against new architectures.  Patch 1/2 has
> been slightly tweaked here:
> 
> http://lkml.kernel.org/r/%3C744e07394a02be3d3ef52c22ccedb24d9a478fe1.1343869850.git.luto@xxxxxxxxxxxxxx%3E
> 
> and will soon appear here (once the cache refreshes)
> 
> https://git.kernel.org/?p=linux/kernel/git/luto/linux.git;a=shortlog;h=refs/heads/seccomp-vsyscall/patch_v2
> 
> I can wait for someone to pick it up or I can send a pull request from
> my tree.  FWIW, the same patch applies cleanly to -next.

You might want to resend them, in patch form, to James, if he's missed
them already.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/