All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvmarm@lists.linux.dev, Joey Gouly <joey.gouly@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH 0/2] KVM: arm64: Fix splat/misbehavior for MMIO SEA injection
Date: Sat, 19 Oct 2024 10:16:26 +0100	[thread overview]
Message-ID: <87y12ktpud.wl-maz@kernel.org> (raw)
In-Reply-To: <20241018194757.3685856-1-oliver.upton@linux.dev>

On Fri, 18 Oct 2024 20:47:55 +0100,
Oliver Upton <oliver.upton@linux.dev> wrote:
> 
> syzkaller continues to find more interesting bugs, this time due to a
> decently-sized hole in our UAPI.
> 
> Turns out we still go through the motions of completing MMIO emulation
> even if userspace has pended a *synchronous* external abort in response
> to an unexpected access. Oops!
> 
> In addition to the fix, I felt this warranted a selftest because a
> documented UAPI flow has been broken for a while.

Indeed. A good indication that nobody is using it.

> Marc, I'll probably take this in 6.13 since we've still got quite a bit
> outstanding for 6.12 and this isn't *terribly* urgent.

Agreed. And the current set of fixes is not going anywhere at the
moment. I may have to resort to an alternative routing for that.

Thanks,

	M.

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

      parent reply	other threads:[~2024-10-19  9:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 19:47 [PATCH 0/2] KVM: arm64: Fix splat/misbehavior for MMIO SEA injection Oliver Upton
2024-10-18 19:47 ` [PATCH 1/2] KVM: arm64: Don't retire aborted MMIO instruction Oliver Upton
2024-10-19  9:10   ` Marc Zyngier
2024-10-19 18:13     ` Oliver Upton
2024-10-18 19:47 ` [PATCH 2/2] KVM: arm64: selftests: Add tests for MMIO external abort injection Oliver Upton
2024-10-18 21:03   ` Oliver Upton
2024-10-19  9:16 ` Marc Zyngier [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y12ktpud.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=oliver.upton@linux.dev \
    --cc=suzuki.poulose@arm.com \
    --cc=yuzenghui@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.