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-next>] [day] [month] [year] [list]
Message-ID: <CAJKSTDwPX3D956yMaNakgjbHSd7hyyU7YbGN-nM=LmR3qXMtxQ@mail.gmail.com>
Date:   Tue, 14 Jan 2020 15:20:35 +0800
From:   xuesong Chen <xuesong1977@...il.com>
To:     linux-kernel@...r.kernel.org
Cc:     xuesong Chen <xuesong1977@...il.com>
Subject: Question about output of kmalloc()

Hello,

Below code snippet in the .ko:

unsigned long *p = (unsigned long *)kmalloc(sizeof(*p), GFP_KERNEL);
printk("Addr of p = 0x%p\n", p);

The output is:
Addr of p = 0x0000000018606ce7

In my mind, during the early day, the p should be 0xfffff...., can
anybody give some tips why the output looks like it's a physical
address?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ