linux-kernel - Re: [PATCH 13/17] staging: lustre: lloop: Fix build failure on ppc64

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: <alpine.LFD.2.20.1604101647340.3112@casper.infradead.org>
Date:	Sun, 10 Apr 2016 16:52:46 +0100 (BST)
From:	James Simmons <jsimmons@...radead.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
cc:	Jeff Mahoney <jeffm@...e.com>, devel@...verdev.osuosl.org,
	Andreas Dilger <andreas.dilger@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Oleg Drokin <oleg.drokin@...el.com>,
	Lustre Development List <lustre-devel@...ts.lustre.org>
Subject: Re: [PATCH 13/17] staging: lustre: lloop: Fix build failure on
 ppc64


> > > This patch was shown not to work. I just haven't removed it from opensuse yet.
> > 
> > Its been running in our production tree as well for some time. Guess that 
> > change is a noop. In any case we have been discussing redoing the lloop 
> > driver anyways. Just need to find the cycles.
> 
> Why do you need this driver?  I know Christoph has pointed out many
> times that it should just be dropped as it's not needed.

Please don't drop this driver just yet. The reason we kept it was for the DIO 
support that the loop back device lacked earlier. We need to do some 
testing to make sure the loop can completely replace this driver.

> And should I drop this patch from the series?

Yes since it is a noop. No other patches are dependent on it.