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] [day] [month] [year] [list]
Message-ID: <b286343d4a17afea491c195920ca0c5d@kernel.org>
Date:   Thu, 03 Sep 2020 11:12:14 +0100
From:   Marc Zyngier <maz@...nel.org>
To:     zc <zoucao@...ux.alibaba.com>
Cc:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        tglx@...utronix.de, jason@...edaemon.net
Subject: Re: [PATCH] irqchip/gic-v3: change gic_data into gic_v3_data

On 2020-09-03 11:05, zc wrote:
>   thank for you reply.
> 
> 
>    of course it won't,   i just think it is better to splite the
> global data between irq-gic and irq-gic-v3.
> 
> I wrote some hook module for gic,  kallsyms_lookup_name can't support
> for mutlipte symbol,
> 
> i need to call kallsyms scan to get the addr.

Why would you need to hook into the GIC data?

>   If you think it isn't necessary, well for me.

I don't think it is necessary for mainline to work correctly,
and I don't understand what you are trying to achieve with this
"hook module".

If you could explain what you are trying to do and why you are
doing it, maybe we can come up with something. But I don't
think blindly repainting symbol names is a sensible course of
action.

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ