linux-kernel - Re: [PATCH 00/23] tracehook

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: <20080717013013.e3f7d7cf.akpm@linux-foundation.org>
Date:	Thu, 17 Jul 2008 01:30:13 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Roland McGrath <roland@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/23] tracehook

On Thu, 17 Jul 2008 01:11:21 -0700 (PDT) Roland McGrath <roland@...hat.com> wrote:

> > It's a strange time to be sending this.
> 
> I've never managed to understand how the timing of your cycles works
> exactly, and I really just work on the "send it when you can" principle.

It's pretty simple - it's just piplining.  During the -rc's we
accumulate stuff for the next release in linux-next and in -mm.  During
the 2.6.x->2.6.x+1-rc1 merge window we transfer that material into
mainline then the cycle starts again.

So new code which turns up during the merge window is a problem.  It
should be reviewed, integrated on top of the already-pending work and
should get some testing in linux-next.  But during the patch-merging
chaos nobody has the time or a suitable tree upon which to be doing
that.

> To be honest all I really know is that stuff is going in now, and that
> I think this stuff of mine is ready to go.

Yes, but all the stuff which is going in now has been reviewed and has
had testing in linux-next and/or -mm.  (In theory).

> > That being said, the impact on existing code is fairly modest and we
> > could perhaps slip it into 2.6.27-rc1.  I haven't looked at it yet.
> 
> I really hope this can be merged in soon (for 2.6.27).  I do think its
> impact is low.  The sooner this goes in, the sooner arch folks can round
> out all their bits and the more time folks like me can spend on actually
> making something new and interesting happen in this area.
> 
> I am happy to do whatever merging/rebasing work helps that happen the
> soonest.  If there is a different GIT tree to branch a rebase from,
> that is easy for me to do.
> 

erk.

Well I got it all merged up relatively easily but I don't know what it
does and I haven't looked at it yet.

It will take some urgent effort from reviewers and, it appears, arch
maintainers to be able to get this over the line.  Even then it wom't
have had any linux-next testing.  This should all have started weeks
ago!

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