linux-kernel - Re: [PATCH 3/4] KVM: renumber architecture-dependent requests

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] [day] [month] [year] [list]

Message-ID: <568F50BE.209@lab.ntt.co.jp>
Date:	Fri, 8 Jan 2016 15:01:34 +0900
From:	Takuya Yoshikawa <yoshikawa_takuya_b1@....ntt.co.jp>
To:	Paolo Bonzini <pbonzini@...hat.com>, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org
Cc:	Christian Borntraeger <borntraeger@...ibm.com>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: [PATCH 3/4] KVM: renumber architecture-dependent requests

On 2016/01/07 23:17, Paolo Bonzini wrote:
> Leave room for 4 more arch-independent requests.

In the current requests handling code, this ordering means
that architecture specific requests get handled only after
generic ones.

If someone wants to make a generic request that needs to be
handled before entering the guest from any architecture
specific request handler, this can be a problem.

If you can guarantee that this kind of dependencies will not
be introduced in the future, this change looks good to me.

Actually, I want to make the current dependencies, even between
architecture specific requests, more explicitly written in the
code.

  Takuya