From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com ([66.111.4.28]:55286 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753561AbcCMA05 (ORCPT ); Sat, 12 Mar 2016 19:26:57 -0500 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D786A20665 for ; Sat, 12 Mar 2016 19:26:56 -0500 (EST) Received: from sigkill.com (c-50-174-131-147.hsd1.ca.comcast.net [50.174.131.147]) by mail.messagingengine.com (Postfix) with ESMTPA id 55BBE6800F3 for ; Sat, 12 Mar 2016 19:26:56 -0500 (EST) Date: Sat, 12 Mar 2016 16:26:54 -0800 From: "J. Paul Reed" To: stable@vger.kernel.org Subject: Fixing userspace crypto in 3.14.x? Message-ID: <20160313002654.GA3563@sigkill.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: stable-owner@vger.kernel.org List-ID: Userspace crypto has been broken in the 3.14 series since 3.14.61; see: http://marc.info/?t=145571848500001&r=1&w=2 Specifically: http://marc.info/?l=linux-crypto-vger&m=145597880120294&w=2 and http://marc.info/?l=linux-crypto-vger&m=145579378307060&w=2 I waited a few 3.14 maintenance releases to see if this would get fixed, but as of 3.14.64, it remains broken. Are there any plans plans to fix this? (For those of us with luks-encrypted partitions, the 3.14 tree is now unusable past 3.14.60.) thanks, preed -- J. Paul Reed PGP: 0xDF8708F8 -- http://www.soberbuildengineer.com ========================================================================= I've never seen an airplane yet that can read the type ratings on your pilot's license. -- Chuck Boedecker