From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199425] BUG: KASAN: use-after-free in drm_atomic_helper_wait_for_flip_done+0x247/0x260
Date: Thu, 21 Jun 2018 13:10:53 +0000 [thread overview]
Message-ID: <bug-199425-2300-P9XsVNCanl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199425-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199425
--- Comment #10 from mikita.lipski@amd.com (mikita.lipski@amd.com) ---
Johannes,
My patch wasn't merged into DRM, but Daniel Vetter proposed another patch that
might remove legacy code that causes the issue. Could you remove my patch from
your tree and apply the following patch:
https://patchwork.freedesktop.org/patch/230355/
Could you please if it fixes the Kasan issue for you, thanks.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-06-21 13:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 8:01 [Bug 199425] New: BUG: KASAN: use-after-free in drm_atomic_helper_wait_for_flip_done+0x247/0x260 bugzilla-daemon
2018-04-25 21:08 ` [Bug 199425] " bugzilla-daemon
2018-05-22 16:34 ` bugzilla-daemon
2018-05-23 17:22 ` bugzilla-daemon
2018-05-23 17:30 ` bugzilla-daemon
2018-05-24 18:33 ` bugzilla-daemon
2018-05-24 20:47 ` bugzilla-daemon
2018-05-25 12:00 ` bugzilla-daemon
2018-05-28 16:01 ` bugzilla-daemon
2018-06-15 14:24 ` bugzilla-daemon
2018-06-21 13:10 ` bugzilla-daemon [this message]
2018-06-27 15:04 ` bugzilla-daemon
2018-07-03 20:57 ` bugzilla-daemon
2018-07-24 19:38 ` bugzilla-daemon
2018-07-25 13:02 ` bugzilla-daemon
2018-07-25 14:12 ` bugzilla-daemon
2018-07-25 16:40 ` bugzilla-daemon
2018-08-17 9:31 ` bugzilla-daemon
2018-08-20 6:28 ` bugzilla-daemon
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=bug-199425-2300-P9XsVNCanl@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/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).