linux-kernel - Re: rt8000usb driver issue (maybe interaction with other drivers)

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] [day] [month] [year] [list]

Message-ID: <CAEXpi5Qw8g2-=FPiSrmh4va22dg6jP8bT2bAcR5WnPUKMD5byA@mail.gmail.com>
Date:   Thu, 5 Oct 2023 14:08:06 -0400
From:   enc0der <enc0der@...il.com>
To:     Stanislaw Gruszka <stf_xl@...pl>
Cc:     Bagas Sanjaya <bagasdotme@...il.com>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Wireless <linux-wireless@...r.kernel.org>
Subject: Re: rt8000usb driver issue (maybe interaction with other drivers)

On Wed, Oct 4, 2023 at 2:28 PM Stanislaw Gruszka <stf_xl@...pl> wrote:

> Here is the issue. We send the frames with spin_lock taken, in such
> case no sleep (i.e. schedule() call) is allowed. Some function from
> tegra/nvhost is actually sleeping, hence the bug.
>
> As already pointed Thorsten, those tegra_/nvhost_ are proprietary functions,
> which are not included in the upstream linux kernel, so we can not fix them.
>
> However I can advice you to detach those from crypto_aead_encrypt,
> this should be doable. At worst your will need to  recompile your
> kernel with those crypto offload engines disabled, but perhaps
> this can be configured dynamically.

Thank you Stanislaw and everyone else for your help, super
appreciated.  I will bring this back to Nvidia as this makes sense to
me the problem is in their upstream changes.  I suspect the person who
was trying to help me just wasn't familiar with all their own changes.

> Regards
> Stanislaw