linux-kernel - Re: [PATCH] drivers/xen/hypervisor: Expose VM SIF flags to userspace

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:   Tue, 29 Nov 2022 16:46:36 +0000
From:   "Per Bilse (3P)" <Per.Bilse@...rix.com>
To:     Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     Juergen Gross <jgross@...e.com>,
        Stefano Stabellini <sstabellini@...nel.org>,
        Oleksandr Tyshchenko <oleksandr_tyshchenko@...m.com>,
        Jan Beulich <jbeulich@...e.com>,
        "moderated list:XEN HYPERVISOR INTERFACE" 
        <xen-devel@...ts.xenproject.org>
Subject: Re: [PATCH] drivers/xen/hypervisor: Expose VM SIF flags to userspace

On 29/11/2022 16:29, Boris Ostrovsky wrote:
> Why not simply show unprocessed xen_start_flags as a hex value?

Providing a text representation follows what is currently the case:

[root@...2-dt128 /proc/xen]# cat capabilities
control_d
[root@...2-dt128 /proc/xen]#

The migrated form would yield:

root@...0:/sys/hypervisor/properties# cat flags
privileged initdomain mod_start_pfn
root@...0:/sys/hypervisor/properties#

There is good precedence for being more helpful than printing hex 
values, but I have no objections if there is consensus that a hex value 
is better.

Best,

   -- Per