linux-kernel - Re: [GIT PULL] notification tree changes for 3.8

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:	Thu, 20 Dec 2012 17:50:26 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Eric Paris <eparis@...hat.com>,
	Lino Sanfilippo <LinoSanfilippo@....de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] notification tree changes for 3.8

On Thu, Dec 20, 2012 at 2:38 PM, Eric Paris <eparis@...hat.com> wrote:
> I believe you would get a build failure after this pull due to the
> addition of procfs information for *notify fds.  The attached patch from
> sfr should be applied during the merge to change the spin_lock in that
> patch to the mutex in this patch.

I'm not going to bother pulling this.

It's coming in late in the merge window, it has been rebased days ago,
and it changes fundamental infrastructure.

This has been a huge merge window, and this is just too late and too
surprising. The commits are marked as being written 18 months ago, but
then the commit date is after the merge window started, and sent the
day before it closes.

WTF? If they've waited 18 months, there cannot be this kind of
last-minute hurry now. Why did you wait until the last minute?

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