public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chintan Patel <chintanlike@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
	maarten.lankhorst@linux.intel.com, maxime.ripard@kernel.org,
	airlied@gmail.com, simona@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	syzbot+147ba789658184f0ce04@syzkaller.appspotmail.com
Subject: Re: [PATCH v4] drm/vblank: Increase timeout in drm_wait_one_vblank()
Date: Wed, 3 Dec 2025 19:44:49 -0800	[thread overview]
Message-ID: <67663eda-dce6-48e7-ad54-572bbce8b944@gmail.com> (raw)
In-Reply-To: <2dae83e3-6fee-4e66-964e-c7baf46eecd8@suse.de>

Hi Thomas,

On 10/28/25 10:14, Thomas Zimmermann wrote:
> 
> 
> Am 28.10.25 um 04:43 schrieb Chintan Patel:
>> Currently, wait_event_timeout() in drm_wait_one_vblank() uses a 100ms
>> timeout. Under heavy scheduling pressure or rare delayed vblank
>> handling, this can trigger WARNs unnecessarily.
>>
>> Increase the timeout to 1000ms to reduce spurious WARNs, while still
>> catching genuine issues.
> 
> Thanks a lot.
> 
>>
>> Reported-by: syzbot+147ba789658184f0ce04@syzkaller.appspotmail.com
>> Closes: https://syzkaller.appspot.com/bug?extid=147ba789658184f0ce04
>> Tested-by: syzbot+147ba789658184f0ce04@syzkaller.appspotmail.com
>> Signed-off-by: Chintan Patel <chintanlike@gmail.com>
> 
> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>

Gentle ping on this patch. Please let me know if there are any issues 
with the patch, or if it requires any changes or further testing.

>>
>> v2:
>>   - Dropped unnecessary in-code comment (suggested by Thomas Zimmermann)
>>   - Removed else branch, only log timeout case
>>
>> v3:
>>   - Replaced drm_dbg_kms()/manual logging with drm_err() (suggested by 
>> Ville Syrjälä)
>>   - Removed unnecessary curr = drm_vblank_count() (suggested by Thomas 
>> Zimmermann)
>>   - Fixed commit message wording ("invalid userspace calls" → "delayed 
>> vblank handling")
>>
>> v4:
>>   - Keep the original drm_WARN() to catch genuine kernel issues
>>   - Increased timeout from 100ms → 1000ms to reduce spurious WARNs 
>> (suggested by Thomas Zimmermann)
>> ---
>>   drivers/gpu/drm/drm_vblank.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/drm_vblank.c b/drivers/gpu/drm/drm_vblank.c
>> index 46f59883183d..f779103b261b 100644
>> --- a/drivers/gpu/drm/drm_vblank.c
>> +++ b/drivers/gpu/drm/drm_vblank.c
>> @@ -1303,7 +1303,7 @@ void drm_wait_one_vblank(struct drm_device *dev, 
>> unsigned int pipe)
>>       ret = wait_event_timeout(vblank->queue,
>>                    last != drm_vblank_count(dev, pipe),
>> -                 msecs_to_jiffies(100));
>> +                 msecs_to_jiffies(1000));
>>       drm_WARN(dev, ret == 0, "vblank wait timed out on crtc %i\n", 
>> pipe);
> 


  parent reply	other threads:[~2025-12-04  3:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28  3:43 [PATCH v4] drm/vblank: Increase timeout in drm_wait_one_vblank() Chintan Patel
2025-10-28 17:14 ` Thomas Zimmermann
2025-10-29  3:50   ` Chintan Patel
2025-12-04  3:44   ` Chintan Patel [this message]
2025-12-04  7:34     ` Thomas Zimmermann

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=67663eda-dce6-48e7-ad54-572bbce8b944@gmail.com \
    --to=chintanlike@gmail.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=maxime.ripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=syzbot+147ba789658184f0ce04@syzkaller.appspotmail.com \
    --cc=tzimmermann@suse.de \
    /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