linux-kernel - Re: Linux 3.3-1 out

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: <20120126014836.aaf79457.akpm@linux-foundation.org>
Date:	Thu, 26 Jan 2012 01:48:36 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-next@...r.kernel.org
Subject: Re: Linux 3.3-1 out - merge window closed

On Fri, 20 Jan 2012 15:14:52 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi all,
> 
> On Thu, 19 Jan 2012 15:58:28 -0800 Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> >
> > (Stats for those that like them: 20% arch updates (arm, power, mips,
> > x86), 60% drivers (networking - wireless in particular, staging,
> > media, dri, sound, misc - including getting rid of 'struct sysdev'),
> > and 20% random stuff: filesystems, networking, perf etc)
> 
> More stats for the bored:
> 
> (I don't count merge commits below and everything is relative to v3.2)
> 
> Of the 8899 commits in v3.3-rc1, 6918 were in next-20120106 (the first
> -next based on v3.2).  A further 792 commits have the same subject line as
> commits in next-20120116 and a further 16 have the same patch-id.
> 
> This leaves 1174 commits (13%) in v3.3-rc1 that were not in next-20120106
> for some reason (not too bad really, I guess).

That's a lot.  Please name names!

I was impacted by several busted patches which had not appeared in
-next.

Also, I saw numerous patches which were significantly altered during
their trip from -next to mainline, which is cheating.  These showed up
as a massive reject storm when I attempted to git-merge linus-now with
next-from-12-hours-ago.  I went in and checked.  tools/perf was a major
culprit.

> Some will clearly be bug
> fixes, of course.  Some will be quilt trees (probably rebased before
> being sent to Linus).  Some will be patches that depend on work by others.

The quilt trees would have been eliminated by the "commits have the
same subject line" test?


I don't think this is all a huuuge problem - we sort this stuff out
fairly quickly.  But things could be improved a bit.
--
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/