All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+f6a46b038fc243ac0175@syzkaller.appspotmail.com>,
	syzkaller@googlegroups.com, catalin.marinas@arm.com,
	joey.gouly@arm.com, kvm@vger.kernel.org, kvmarm@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, oupton@kernel.org,
	suzuki.poulose@arm.com, syzkaller-bugs@googlegroups.com,
	will@kernel.org, yuzenghui@huawei.com
Subject: Re: [syzbot] [kvmarm?] [kvm?] BUG: unable to handle kernel paging request in kvm_vgic_destroy
Date: Mon, 02 Mar 2026 13:26:30 +0000	[thread overview]
Message-ID: <86wlzu8ird.wl-maz@kernel.org> (raw)
In-Reply-To: <CACT4Y+bbQ3qfoy0kuXgTk5H2k=Wrg2t0Ghhc6U6fT-28ter7iA@mail.gmail.com>

Hi Dmitry,

On Mon, 02 Mar 2026 12:59:41 +0000,
Dmitry Vyukov <dvyukov@google.com> wrote:
> 
> Hi Marc,
> 
> The reproducer should print at the start specifically to address this concern:
> 
> the reproducer may not work as expected: fault injection setup failed:
> failed to write fault injection file
> 
> Isn't it enough?

Ah, I totally missed that, because things scroll really
quickly... Apologies.

I think it'd be a bit better to just stop the test if the
preconditions are not met, as nothing useful will happen.

Thanks,

	M.

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

      reply	other threads:[~2026-03-02 13:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 11:46 [syzbot] [kvmarm?] [kvm?] BUG: unable to handle kernel paging request in kvm_vgic_destroy syzbot
2026-02-28 14:55 ` Marc Zyngier
2026-02-28 15:57   ` syzbot
2026-03-02 12:59   ` Dmitry Vyukov
2026-03-02 13:26     ` 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=86wlzu8ird.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=dvyukov@google.com \
    --cc=joey.gouly@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oupton@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=syzbot+f6a46b038fc243ac0175@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=syzkaller@googlegroups.com \
    --cc=will@kernel.org \
    --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.