netdev - Re: [PATCH net-next 0/2] Fixing issues in dma mapping and driver removal

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20200610.170543.194012331092190844.davem@davemloft.net>
Date:   Wed, 10 Jun 2020 17:05:43 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     ayush.sawal@...lsio.com
Cc:     herbert@...dor.apana.org.au, netdev@...r.kernel.org,
        manojmalviya@...lsio.com
Subject: Re: [PATCH net-next 0/2] Fixing issues in dma mapping and driver
 removal

From: Ayush Sawal <ayush.sawal@...lsio.com>
Date: Wed, 10 Jun 2020 02:54:30 +0530

> Patch 1: This fixes the kernel panic which occurs due to the accessing
> of a zero length sg.
> 
> Patch 2: Avoiding unregistering the algorithm if cra_refcnt is not 1.
> 
> Ayush Sawal (2):
>   Crypto/chcr: Calculate src and dst sg lengths separately for dma map
>   Crypto/chcr: Checking cra_refcnt before unregistering the algorithms

Series applied, thanks.

Maybe we can start handling these changes via the crypto tree at some
point?