From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Muir Subject: Re: bug: msm8998, ecryptfs, cannot create files due to invalid keysize Date: Tue, 21 Nov 2017 10:33:46 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from mail-lf0-f65.google.com ([209.85.215.65]:41971 "EHLO mail-lf0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751322AbdKUPds (ORCPT ); Tue, 21 Nov 2017 10:33:48 -0500 Received: by mail-lf0-f65.google.com with SMTP id f134so14591916lfg.8 for ; Tue, 21 Nov 2017 07:33:48 -0800 (PST) In-Reply-To: Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: linux-arm-msm@vger.kernel.org Cc: ecryptfs@vger.kernel.org On Fri, Oct 27, 2017 at 4:43 PM, James Muir wrote: > There were some changes made in the msm linux kernel (msm8998) to add > hw support to ecryptfs. > > Unfortunately, those changes break basic ecryptfs usage; > This regression was introduced in the following commit: > > https://github.com/sonyxperiadev/kernel/commit/8928f8683bcd0236f5653963deee3bc225fb2206 > > That commit is also present in aosp (e.g. the Pixel 2 uses the > msm8998; but note that the aosp kernels do not enable ecryptfs). Since my message was essentially a bug report (without a patch), it might be that linux-arm-msm was not the right place to submit it. Does anyone know of a better way to report msm kernel bugs to Qualcomm? Due to the high volume of traffic on the list, it seems likely a bug report would get overlooked here. -James M