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  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]
Date:   Thu, 23 Sep 2021 15:13:53 +0200
From:   Greg KH <>
To:     Guo Zhi <>
        kan liang <>,,,,,,
        linux-kernel <>
Subject: Re: [PATCH] staging: vchip_arm: Fix misuse of %x

Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

On Thu, Sep 23, 2021 at 08:57:40PM +0800, Guo Zhi wrote:
> We should restrict kernel pointer leakage issue by using kptr_restrict. 
> Therefore kernel pointers should be specified by %pK rather than %lx.

I totally agree.

What I am asking about is why is this message needed at all?  Why not
just remove the whole thing?  Who uses it?


greg k-h

Powered by blists - more mailing lists