linux-kernel - Re: [PATCH] csky: Fixup ioremap function losing

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

Message-ID: <CAJF2gTTBc3+SnKMbVU4A+tekyjkd_7XUmDCUfNCcA-CZf=JUyg@mail.gmail.com>
Date:   Sun, 18 Aug 2019 10:20:18 +0800
From:   Guo Ren <guoren@...nel.org>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     Arnd Bergmann <arnd@...db.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-arch <linux-arch@...r.kernel.org>,
        linux-csky@...r.kernel.org, zhang_jian5@...uatech.com,
        Guo Ren <ren_guo@...ky.com>
Subject: Re: [PATCH] csky: Fixup ioremap function losing

Thx Christoph,

On Fri, Aug 16, 2019 at 3:03 PM Christoph Hellwig <hch@...radead.org> wrote:
>
> On Thu, Aug 15, 2019 at 07:28:57PM +0800, guoren@...nel.org wrote:
> > From: Guo Ren <ren_guo@...ky.com>
> >
> > Implement the following apis to meet usage in different scenarios.
> >
> >  - ioremap          (NonCache + StrongOrder)
> >  - ioremap_nocache  (NonCache + StrongOrder)
> >  - ioremap_wc       (NonCache + WeakOrder  )
> >  - ioremap_cache    (   Cache + WeakOrder  )
> >
> > Also change flag VM_ALLOC to VM_IOREMAP in get_vm_area_caller.
>
> Looks generally fine, but two comments:
>
>  - do you have a need for ioremap_cache?  We are generally try to
>    phase it out in favour of memremap, and it is generally only used
>    by arch specific code.
Yes, some drivers of our customers use ioremap_cache to map phy_addr
which isn't belong to system memory.

>  - I have a big series pending to clean up the mess with our
>    ioremap_* functions, including adding a generic implementation
>    that csky should be able to use.  Unless this patch is urgent it
>    might make sense to rebase it on top.  Here is my current tree, I
>    plan to post it soon:
>
>         http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/generic-ioremap
I agree to use GENERIC_IOREMAP, but I want to add csky support
GENERIC_IOREMAP patch by myself.
You could remove "csky: use generic ioremap" in your patchset first
and I'll add support GENERIC_IORMAP patch later.
Then we won't get confilct :)

--
Best Regards
 Guo Ren

ML: https://lore.kernel.org/linux-csky/