From: syzbot <syzbot+0948c82180d475ad24e2@syzkaller.appspotmail.com>
To: souradiptodas6@gmail.com
Cc: souradiptodas6@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: #syz test
Date: Wed, 20 May 2026 01:48:31 -0700 [thread overview]
Message-ID: <6a0d755f.170a0220.3cbd30.013f.GAE@google.com> (raw)
In-Reply-To: <20260520084826.6246-1-souradiptodas6@gmail.com>
> From c3f773691e3c568d67d8628ffd4b7cf25ba8e150 Mon Sep 17 00:00:00 2001
> From: Souradipto Das <souradiptodas6@gmail.com>
> Date: Wed, 20 May 2026 14:11:05 +0530
> Subject: [PATCH] #syz test KVM: x86/xen: Secure gpc refresh_lock mutual
> exclusion in shared info init
>
> ---
> arch/x86/kvm/xen.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/x86/kvm/xen.c b/arch/x86/kvm/xen.c
> index 91fd3673c09a..421e4359ce0d 100644
> --- a/arch/x86/kvm/xen.c
> +++ b/arch/x86/kvm/xen.c
> @@ -45,6 +45,8 @@ static int kvm_xen_shared_info_init(struct kvm *kvm)
> int ret = 0;
> int idx = srcu_read_lock(&kvm->srcu);
>
> + mutex_lock(&gpc->refresh_lock);
> +
> read_lock_irq(&gpc->lock);
> while (!kvm_gpc_check(gpc, PAGE_SIZE)) {
> read_unlock_irq(&gpc->lock);
> @@ -101,6 +103,7 @@ static int kvm_xen_shared_info_init(struct kvm *kvm)
> kvm_make_all_cpus_request(kvm, KVM_REQ_MASTERCLOCK_UPDATE);
>
> out:
> + mutex_unlock(&gpc->refresh_lock);
> srcu_read_unlock(&kvm->srcu, idx);
> return ret;
> }
> --
> 2.43.0
>
This crash does not have a reproducer. I cannot test it.
next parent reply other threads:[~2026-05-20 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260520084826.6246-1-souradiptodas6@gmail.com>
2026-05-20 8:48 ` syzbot [this message]
[not found] <CAKZCeSX=JVK5OK0GLYry4gkEH9cryp-FG8k9WcR_6FsPsZR6JQ@mail.gmail.com>
2026-02-08 20:03 ` syzbot
2026-02-08 20:09 ` kawada
2026-02-09 7:50 ` kawada
2025-11-10 18:41 [syzbot] [bpf?] KASAN: stack-out-of-bounds Write in __bpf_get_stack syzbot
2026-01-04 18:29 ` #syz test Arnaud Lecomte
2026-01-04 18:30 ` Arnaud Lecomte
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=6a0d755f.170a0220.3cbd30.013f.GAE@google.com \
--to=syzbot+0948c82180d475ad24e2@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=souradiptodas6@gmail.com \
--cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome