Date: Thu, 1 Mar 2012 21:41:51 -0600 From: Will Drewry <wad@...omium.org> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: Kees Cook <keescook@...omium.org>, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org, linux-doc@...r.kernel.org, kernel-hardening@...ts.openwall.com, netdev@...r.kernel.org, x86@...nel.org, arnd@...db.de, davem@...emloft.net, hpa@...or.com, mingo@...hat.com, oleg@...hat.com, peterz@...radead.org, rdunlap@...otime.net, mcgrathr@...omium.org, tglx@...utronix.de, luto@....edu, eparis@...hat.com, serge.hallyn@...onical.com, djm@...drot.org, scarybeasts@...il.com, indan@....nu, pmoore@...hat.com, corbet@....net, eric.dumazet@...il.com, markus@...omium.org, coreyb@...ux.vnet.ibm.com Subject: Re: [PATCH v12 01/13] sk_run_filter: add support for custom load_pointer On Thu, Mar 1, 2012 at 9:10 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote: > Hi Kees, > > On Thu, 1 Mar 2012 16:57:49 -0800 Kees Cook <keescook@...omium.org> wrote: >> >> Unfortunately, yes, it does -- there were both ptrace changes and prctl changes. >> >> And at least the ptrace changes are, IIRC, in -mm, which has no tree. >> :P Given that, what's the best thing for me to do for this to be easy >> for you to pull? > > Does this set of patches *depend* on functionality provided by those, or > just produce conflicts against the other changes? If it is just > conflicts, then base your tree on Linus and I and (he when it comes to > it) can fix the conflicts as needed (with some hints if you think it is a > good idea i.e. is the conflicts are particularly complex). No explicit dependency. It's just a conflict in how ptrace options are set, defined, and masked (and STOP being renumbered). Other than the ptrace changes, the whole series patches cleanly onto both trees. The resolved version is less code and easier to read, so I don't suspect it'll be a challenge at all. thanks!
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.