linux-kernel - Re: [PATCH 17/18] fs: icache remove inode

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: <20101015153817.GA7796@amd>
Date:	Sat, 16 Oct 2010 02:38:17 +1100
From:	Nick Piggin <npiggin@...nel.dk>
To:	Dave Chinner <david@...morbit.com>
Cc:	Nick Piggin <npiggin@...nel.dk>,
	Christoph Hellwig <hch@...radead.org>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 17/18] fs: icache remove inode_lock

On Fri, Oct 15, 2010 at 10:33:36PM +1100, Dave Chinner wrote:
> So, Nick, please, either help us get the code into a form acceptible
> to the VFS maintainers and into mainline, or stay out of the way
> while we go through the process as quickly as we can. This requireѕ
> a co-ordinated group effort, so arguing is really quite
> counter-productive. I'd prefer that you help us get through the
> process by being constructive and reviewing and testing and keeping
> us honest.

This exact same statement applies to you, from me. We all know
how to cooperate, and forking a new tree because the maintainer
goes away for a few weeks (and you suddenly get interested after
all this time) is not the right way to do it.

Frankly if your attitude is now demanding that I cooperate with
you, then I'm actually quite happy to just go over your head.

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