linux-kernel - RE: [PATCH v2 1/2] habanalabs: support kernel memory mapping

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]

Date:   Mon, 11 Nov 2019 06:37:46 +0000
From:   Omer Shpigelman <oshpigelman@...ana.ai>
To:     Christoph Hellwig <hch@...radead.org>
CC:     "oded.gabbay@...il.com" <oded.gabbay@...il.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2 1/2] habanalabs: support kernel memory mapping

On Wed, Oct 24, 2019 at 01:39 PM, Omer Shpigelman wrote:
> On Thu, Oct 24, 2019 at 04:29 AM Christoph Hellwig <hch@...radead.org>
> wrote:
> > On Wed, Oct 23, 2019 at 01:39:41PM +0000, Omer Shpigelman wrote:
> > > I'm not sure I understand. Can you please pin point the problematic line?
> >
> > Every line you touch addr field basically.  If you have a kernel
> > address please store it in an actual C pointer type, not in a u64 to
> > ensure that the compiler can do proper type checking.
> 
> I see your point. I'll separate the code so the kernel address path will use a
> pointer type rather than u64.

Due to a change in the requirements for future ASICs support, there is no need in mapping vmalloc memory.
As a result this patch is discarded.