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]
Date:	Mon, 12 Apr 2010 22:32:23 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Oleg Nesterov <oleg@...hat.com>, John Kacur <jkacur@...il.com>,
	Roland McGrath <roland@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Arnd Bergmann <arnd@...db.de>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] ptrace: kill BKL in ptrace syscall

On Mon, Apr 12, 2010 at 01:29:10PM -0700, Andrew Morton wrote:
> On Thu, 1 Apr 2010 20:48:58 +0200
> Frederic Weisbecker <fweisbec@...il.com> wrote:
> 
> > On Mon, Mar 29, 2010 at 08:35:02PM +0200, Oleg Nesterov wrote:
> > > On 03/29, Frederic Weisbecker wrote:
> > > >
> > > > On Mon, Mar 29, 2010 at 03:26:26PM +0200, John Kacur wrote:
> > > > > On Mon, Mar 29, 2010 at 3:05 PM, Oleg Nesterov <oleg@...hat.com> wrote:
> > > > > >
> > > > > > Cough. I must admit, apart from "urgent" bugfixes the only way I know
> > > > > > is to send the patch to Andrew.
> > > > > >
> > > > > > So I'd suggest to send this patch to akpm. Of course, if you wish I can
> > > > > > forward it, but doesn't matter.
> > > > > >
> > > > > I know that in the past, Thomas was keeping a BKL tree in tip, but not sure if
> > > > > he is still doing so. It seems that Arnd's tree is at least partially
> > > > > experimental,
> > > > > so I wonder if we need to maintain another BKL tree somewhere of fixes
> > > > > that have no
> > > > > obvious maintainer, but are ready to send to Linus for inclusion?
> > > >
> > > >
> > > > I have cc'ed Andrew for this patch, partly for that purpose, so that he
> > > > can take it if he wants to.
> > > 
> > > Ah, good, I didn't notice.
> > > 
> > > If he doesn't pick this patch now, I'll forward it to him later again ;)
> > > 
> > > > But in the worst case these patches are never lost. We don't want to lose
> > > > them. For those that can't go in someone else .35 targeted tree for any reason,
> > > > I can queue them up in mine in a dedicated branch that I'll propose to Linus.
> > > 
> > > Frederic, whatever is more convenient to you.
> > > 
> > > Oleg.
> > > 
> > 
> > 
> > I have applied it to:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> > 	bkl/core
> > 
> 
> It hasn't turned up in linux-next yet?


I've asked Stephen two days ago:
http://lkml.org/lkml/2010/4/10/42

I guess this is going to show up in -next soon.

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