linux-kernel - Re: [PATCH] ptrace: kill BKL in ptrace syscall

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

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:
> > On 03/29, John Kacur wrote:
> >>
> >> So, just to be clear about this particular patch, who is queuing it up
> >> to send to Linus? Would that be you Oleg, as a ptrace maintainer?
> >
> > 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.
> >
> > Oleg.
> >
> 
> 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.

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.


> 
> For fixes that have obvious maintainers though, I would just rather go through
> the normal route.


Exactly, as far as there is an active maintainer in the area concerned by a
random kill-bkl patch, I much prefer this patch goes to this maintainer.
It gives a much better passport for this patch, and it avoids possible
future conflicts in this area of code, less work for Stephen :)

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