All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+622bba18029bcde672e1@syzkaller.appspotmail.com>
To: airlied@gmail.com, astrajoan@yahoo.com, daniel@ffwll.ch,
	 davem@davemloft.net, dri-devel@lists.freedesktop.org,
	dsahern@kernel.org,  edumazet@google.com,
	ivan.orlov0322@gmail.com, jacob.e.keller@intel.com,
	 jiri@nvidia.com, kuba@kernel.org, linux-kernel@vger.kernel.org,
	 maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	netdev@vger.kernel.org,  pabeni@redhat.com,
	skhan@linuxfoundation.org, syzkaller-bugs@googlegroups.com,
	 tzimmermann@suse.de
Subject: Re: [syzbot] [dri?] divide error in drm_mode_vrefresh
Date: Sat, 08 Jul 2023 21:09:35 -0700	[thread overview]
Message-ID: <000000000000ae45de0600060878@google.com> (raw)
In-Reply-To: <20230709011213.17890-1-astrajoan@yahoo.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+622bba18029bcde672e1@syzkaller.appspotmail.com

Tested on:

commit:         1c7873e3 mm: lock newly mapped VMA with corrected orde..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=101196d2a80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8f6b0c7ae2c9c303
dashboard link: https://syzkaller.appspot.com/bug?extid=622bba18029bcde672e1
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10e44354a80000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2023-07-09  4:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 15:11 [syzbot] [dri?] divide error in drm_mode_vrefresh syzbot
2023-07-09  1:12 ` [PATCH] drm/modes: Fix division by zero error Ziqi Zhao
2023-07-09  1:12   ` Ziqi Zhao
2023-07-09  4:09   ` syzbot [this message]
2023-07-21 16:07   ` Ziqi Zhao
2023-07-21 16:07     ` Ziqi Zhao
2023-08-01  9:30     ` Jani Nikula
2023-08-01 21:55 ` [Intel-gfx] [PATCH v2] " Ziqi Zhao
2023-08-01 21:55   ` Ziqi Zhao
2023-08-01 21:55   ` Ziqi Zhao
2023-08-02 10:04   ` Jani Nikula
2023-08-02 10:04     ` Jani Nikula
2023-08-02 13:24 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-08-02 13:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-02 17:28 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-02 17:47 ` [Intel-gfx] [PATCH v3] drm/modes: Fix division by zero due to overflow Ziqi Zhao
2023-08-02 17:47   ` Ziqi Zhao
2023-08-02 17:47   ` Ziqi Zhao
2023-08-03  9:35   ` Jani Nikula
2023-08-03  9:35     ` Jani Nikula

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=000000000000ae45de0600060878@google.com \
    --to=syzbot+622bba18029bcde672e1@syzkaller.appspotmail.com \
    --cc=airlied@gmail.com \
    --cc=astrajoan@yahoo.com \
    --cc=daniel@ffwll.ch \
    --cc=davem@davemloft.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=ivan.orlov0322@gmail.com \
    --cc=jacob.e.keller@intel.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=skhan@linuxfoundation.org \
    --cc=syzkaller-bugs@googlegroups.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 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.