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]
Message-ID: <877c98u8zq.wl-maz@kernel.org>
Date: Tue, 12 Nov 2024 08:55:21 +0000
From: Marc Zyngier <maz@...nel.org>
To: Jiaqi Yan <jiaqiyan@...gle.com>
Cc: oliver.upton@...ux.dev,
	joey.gouly@....com,
	suzuki.poulose@....com,
	yuzenghui@...wei.com,
	catalin.marinas@....com,
	will@...nel.org,
	pbonzini@...hat.com,
	linux-arm-kernel@...ts.infradead.org,
	kvmarm@...ts.linux.dev,
	kvm@...r.kernel.org,
	duenwen@...gle.com,
	rananta@...gle.com,
	James Houghton <jthoughton@...gle.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v1] KVM: arm64: Introduce KVM_CAP_ARM_SIGBUS_ON_SEA

On Fri, 08 Nov 2024 21:18:50 +0000,
Jiaqi Yan <jiaqiyan@...gle.com> wrote:
> 
> There is also a kernel config called ARM64_RAS_EXTN but I believe it
> is for the host CPU, not about VM's RAS.
> 
> But taking Oliver's opinion into account, I think we want to remove
> KVM_CAP_ARM_SIGBUS_ON_SEA. Wonder what your thoughts are.

If we stick to a signal-based signalling (which I still dislike with a
burning passion), then I agree it can be removed, as this is no
different from a signal being delivered from the rest of the kernel.

	M.

-- 
Without deviation from the norm, progress is not possible.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ