lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jL0OXR5MOePFe=GT4_X5rdH8RNjQPqYXdbqsqfijUsEqA@mail.gmail.com>
Date:	Thu, 1 Mar 2012 16:57:49 -0800
From:	Kees Cook <keescook@...omium.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	akpm@...ux-foundation.org, Will Drewry <wad@...omium.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

Hi,

On Thu, Mar 1, 2012 at 4:47 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Kees,
>
> On Thu, 1 Mar 2012 15:37:12 -0800 Kees Cook <keescook@...omium.org> wrote:
>>
>> Is it time to pull this into -next so more people can feel it? I brought
>> Andy Lutomirski's patches forward (needed to bump the prctl values), and
>> updated my git tree. If we're ready, here it is in all its request-pull
>> format glory:
>>
>> The following changes since commit 2422c8368337196594265d52cad7316c9404bfcf:
>>   Stephen Rothwell (1):
>>         Add linux-next specific files for 20120301
>
> OK, not commenting on anything else, but I cannot merge that into
> linux-next because it is based on yesterday's linux-next release and
> linux-next (effectively) rebases every day ...
>
> Does this work depend on anything in linux-next?  Or could it be just
> based off Linus' tree.  If it depends on other tree(s) merged into
> linux-next, then you should base your tree on those tree(s) as long as
> they never get rebased ...

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?

-Kees

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ