linux-kernel - RE: [RFC] vsprintf: compile error on %09pK

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]

Date:   Mon, 3 Apr 2023 16:04:49 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     'Jaewon Kim' <jaewon31.kim@...il.com>,
        Petr Mladek <pmladek@...e.com>
CC:     Jaewon Kim <jaewon31.kim@...sung.com>,
        "senozhatsky@...omium.org" <senozhatsky@...omium.org>,
        "linux-mm@...ck.org" <linux-mm@...ck.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "GyeongHwan Hong" <gh21.hong@...sung.com>
Subject: RE: [RFC] vsprintf: compile error on %09pK

From: Jaewon Kim
> Sent: 03 April 2023 15:40
...
> I wanted to print phys_addr_t  type value only when kptr_restrict sysctl is
> allowed. So I thought I could use %pK for that purpose. And the physical
> address is not that long. I wanted to make that length short like 9 hex.

Isn't that is the wrong format for physical addresses anyway?
They can be larger than virtual ones (eg x86 with PAE).

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)