linux-kernel - Re: [PATCH v3 09/31] arm64: Cache maintenance routines

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20120914165331.GA2927@arm.com>
Date:	Fri, 14 Sep 2012 17:53:32 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Nicolas Pitre <nico@...xnic.net>
Cc:	Arnd Bergmann <arnd@...db.de>,
	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 09/31] arm64: Cache maintenance routines

On Mon, Sep 10, 2012 at 06:29:21PM +0100, Nicolas Pitre wrote:
> On Mon, 10 Sep 2012, Catalin Marinas wrote:
> 
> > On Fri, Sep 07, 2012 at 08:28:09PM +0100, Arnd Bergmann wrote:
> > > On Friday 07 September 2012, Catalin Marinas wrote:
> > > > +
> > > > +/*
> > > > + *	dmac_inv_range(start,end)
> > > 
> > > all of these appear to be unused now. Can you remove them?
> > 
> > They aren't currently used but I expect some partners to make use of
> > them on their private development. I could drop them from the upstream
> > branch temporarily.
> 
> Depends.  If your expectation from those partners is a real probability 
> then it is best to keep a skeleton in place for them to use, otherwise 
> they might get ... creative.  If this is just wild speculation then you 
> should drop it.

I dropped them for now since there is no API using those functions. But
I have a feeling they will be needed at some point (so I'll keep the
patches around).

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