linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+10328e8428a896b65119@syzkaller.appspotmail.com>
To: airlied@linux.ie, daniel@ffwll.ch,
	dri-devel@lists.freedesktop.org, igormtorrente@gmail.com,
	linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com,
	mripard@kernel.org, syzkaller-bugs@googlegroups.com,
	tzimmermann@suse.de, ztong0001@gmail.com
Subject: Re: [syzbot] general protection fault in drm_client_buffer_vunmap
Date: Sun, 11 Apr 2021 05:01:04 -0700	[thread overview]
Message-ID: <000000000000c4cba105bfb126a1@google.com> (raw)
In-Reply-To: <00000000000086f79105b5553f1e@google.com>

syzbot suspects this issue was fixed by commit:

commit 874a52f9b693ed8bf7a92b3592a547ce8a684e6f
Author: Tong Zhang <ztong0001@gmail.com>
Date:   Sun Feb 28 04:46:25 2021 +0000

    drm/fb-helper: only unmap if buffer not null

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=10c27b7ed00000
start commit:   c03c21ba Merge tag 'keys-misc-20210126' of git://git.kerne..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=ec4c85e44cc3172e
dashboard link: https://syzkaller.appspot.com/bug?extid=10328e8428a896b65119
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12d95d7ad00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=148da9ccd00000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: drm/fb-helper: only unmap if buffer not null

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2021-04-11 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 16:10 general protection fault in drm_client_buffer_vunmap syzbot
2021-04-11 12:01 ` syzbot [this message]
2021-04-11 18:10   ` [syzbot] " 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=000000000000c4cba105bfb126a1@google.com \
    --to=syzbot+10328e8428a896b65119@syzkaller.appspotmail.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=igormtorrente@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tzimmermann@suse.de \
    --cc=ztong0001@gmail.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;
as well as URLs for NNTP newsgroup(s).