From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f200.google.com (mail-oi1-f200.google.com [209.85.167.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 328413BB123 for ; Wed, 13 May 2026 21:41:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.200 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778708472; cv=none; b=HKPJ50uinNJ00S2fVFE7YXqQXDcRb+vM8GLt1Rs1nKAkdWAU4fWCufpgw7KzYJqvVbJPgILEQicTIpnLlLMOLPp8O0yZBFGbNxbG6tbdgUYnIs9vqbbaWgoGvk76FEuXQ01d1OHfyG5N/utdR650ykPjCaykTRLyYHqUtCr/cgk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778708472; c=relaxed/simple; bh=cGXqcrOJv/yyElce22I9PLZQTvhW2A8Q4mBvFtC4P1o=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To:Cc: Content-Type; b=fkBvhCPXX9gcgA8GBx6dl0Mugt9e67mpB+n0u5jPgsCn/S/7T39KOpiOKBQwalkjautPr0vtia7r9reIDym46BNYPrGnMyglYhij4MA9HiLKcrvujb1Wb8+TEkUK06bInIjvcz0Ds8SWMD4XGpOMfcxDxD68ySgUWvVQMoJorgk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.167.200 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oi1-f200.google.com with SMTP id 5614622812f47-482ac93cc7aso2053288b6e.1 for ; Wed, 13 May 2026 14:41:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1778708470; x=1779313270; h=cc:to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Tqk0Slr65mDNKAZF2Vaic14WCI6WBEKE9EJXBGKW5II=; b=r2nRA3QsgvvUkF6n1iJ6xVal/1x+7XeqX/sWTD28qIqIW1JkE1+e88lTPmNngbPgA3 qZIbPHPpMt/ideC/rvO1+19Ze9iUjzhQVOTZOIj0y0RHcQnGYLicSmc7es6uVuHyleos g8JI+HRmMNWvkEPvaBeG4/7fkyuLljjzMBcnnAgIUU1fks4C6bdTEmgewu2cxbHEV69p 10hAHGSajlFJGuiD0SJTkm7tQW366jC3LeA7e2BG6VgTlL7YO2+o3NJPPJ2/MRn82ris QA9X9pXtlnqrDmARc8w7bcTavsjbuhoqAI2oKUFg+q3nQ5hh9u9PqCj9SQ70YPOIKDVv gUMg== X-Forwarded-Encrypted: i=1; AFNElJ+ku8RsS1Fgsq3wyRctmPHH942csYtFbaXMB5DpKJvL+Y2CwmKzNLbzqEfTvNZlos3g6qPEUQnXCTkjphk=@vger.kernel.org X-Gm-Message-State: AOJu0Yx/WjbX9bQDZyD4K3KgdJZOdWoUa91TFbTDvMgzAwBSYF769QjQ Cw/fLceRjB7SnhsBadzZBO1AcMDvGUOYrOT5LRhR3smpDr8deV4JJC4UZijM6DOdTI7pIOG/1bD PVpW3osb1yIedym2gREYw4wAmUtHH1cmShBdr+kOLBfVVGoVwTAnmUStSIhA= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:2902:b0:696:2038:82d7 with SMTP id 006d021491bc7-69b78d5922cmr2866345eaf.23.1778708470301; Wed, 13 May 2026 14:41:10 -0700 (PDT) Date: Wed, 13 May 2026 14:41:10 -0700 In-Reply-To: <82aeba42-7872-4e92-ade8-2b7b6a8a5e43@collabora.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a04eff6.170a0220.14b6e7.0321.GAE@google.com> Subject: Re: [PATCH] drm/virtio: add timeout to virtqueue wait to avoid hung task From: syzbot To: dmitry.osipenko@collabora.com Cc: airlied@redhat.com, dmitry.osipenko@collabora.com, dri-devel@lists.freedesktop.org, gurchetansingh@chromium.org, kraxel@redhat.com, linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com, mripard@kernel.org, olvaffe@gmail.com, ryasuoka@redhat.com, simona@ffwll.ch, tzimmermann@suse.de, virtualization@lists.linux.dev Content-Type: text/plain; charset="UTF-8" > Hi, > > On 5/12/26 11:59, Ryosuke Yasuoka wrote: >> virtio_gpu_queue_ctrl_sgs() and virtio_gpu_queue_cursor() use >> wait_event() without timeout when waiting for virtqueue space. If the >> host device stops processing commands, these waits block indefinitely. >> Since callers may hold DRM locks, this can make the entire system >> unresponsive. >> >> Replace wait_event() with wait_event_timeout() using a 5-second timeout, >> consistent with the existing timeout pattern in the driver. On timeout, >> clean up and return -ENODEV, following the same error path as >> drm_dev_enter() failure. >> >> Reported-by: syzbot+d6dd6f86d3aaf7eebe7406e45c1c6e549453f224@syzkaller.appspotmail.com >> Closes: https://syzkaller.appspot.com/bug?id=d6dd6f86d3aaf7eebe7406e45c1c6e549453f224 >> Reported-by: syzbot+908bd910da5dd79b88de4cf7baf376cc873a922e@syzkaller.appspotmail.com >> Closes: https://syzkaller.appspot.com/bug?id=908bd910da5dd79b88de4cf7baf376cc873a922e >> Signed-off-by: Ryosuke Yasuoka >> --- >> drivers/gpu/drm/virtio/virtgpu_vq.c | 20 ++++++++++++++++++-- >> 1 file changed, 18 insertions(+), 2 deletions(-) > > If host stops processing commands, this is a problem on host side. Isn't it? > > -- > Best regards, > Dmitry I see the command but can't find the corresponding bug. The email is sent to syzbot+HASH@syzkaller.appspotmail.com address but the HASH does not correspond to any known bug. Please double check the address.