All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Muir <james.muir@graphitesoftware.com>
To: Tyler Hicks <tyhicks@canonical.com>
Cc: linux-arm-msm@vger.kernel.org, ecryptfs@vger.kernel.org
Subject: Re: bug: msm8998, ecryptfs, cannot create files due to invalid keysize
Date: Tue, 28 Nov 2017 10:22:26 -0500	[thread overview]
Message-ID: <CAL=R1-=9g2yqhqCS_MJxV8WD537c0CRjzFxRaG-3nSbj03an2Q@mail.gmail.com> (raw)
In-Reply-To: <5092f3db-d574-43e7-dec9-5662a2ee3e3e@canonical.com>

On Mon, Nov 27, 2017 at 1:04 PM, Tyler Hicks <tyhicks@canonical.com> wrote:
> On 11/21/2017 09:33 AM, James Muir wrote:
>> On Fri, Oct 27, 2017 at 4:43 PM, James Muir
>> <james.muir@graphitesoftware.com> 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;
>>
>> <snip>
>>
>>> 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?
>
> I can't help here but it might be useful to directly contact the author
> of the patch that introduced the regression.

Thanks, Tyler.

Contacting the author was the first thing I did.  I sent email on 17
Oct and then again on 6 Nov.  Unfortunately, they have not been
responsive.

I may try reaching out to some of the other msm devs who have made
changes under fs/ecryptfs.

-James M

      reply	other threads:[~2017-11-28 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 20:43 bug: msm8998, ecryptfs, cannot create files due to invalid keysize James Muir
2017-11-21 15:33 ` James Muir
2017-11-27 18:04   ` Tyler Hicks
2017-11-28 15:22     ` James Muir [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAL=R1-=9g2yqhqCS_MJxV8WD537c0CRjzFxRaG-3nSbj03an2Q@mail.gmail.com' \
    --to=james.muir@graphitesoftware.com \
    --cc=ecryptfs@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=tyhicks@canonical.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.