From: Dave Hansen <dave.hansen@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Vince Weaver <vincent.weaver@maine.edu>,
linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [perf] perf_fuzzer triggers NULL pointer derefernce in i915 driver
Date: Fri, 13 Dec 2019 11:20:39 -0800 [thread overview]
Message-ID: <f2c6502a-f13e-a663-f1f5-c441964d77ac@intel.com> (raw)
In-Reply-To: <87tv641z20.fsf@intel.com>
On 12/12/19 11:09 PM, Jani Nikula wrote:
> On Thu, 12 Dec 2019, Vince Weaver <vincent.weaver@maine.edu> wrote:
>> with current git the perf_fuzzer was able to trigger this NULL pointer
>> de-reference in the i915 driver.
> Please file a bug.
>
> https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs
I'm seeing the same thing. It's annoyingly and immediately reproducible
for me:
https://gitlab.freedesktop.org/drm/intel/issues/826
Let me know if you want anything fancier done like a bisect. Looking
back through my kernel logs, it appears to also have happened with
5.4.0-rc4.
next prev parent reply other threads:[~2019-12-13 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 15:36 [perf] perf_fuzzer triggers NULL pointer derefernce in i915 driver Vince Weaver
2019-12-13 7:09 ` Jani Nikula
2019-12-13 19:20 ` Dave Hansen [this message]
2019-12-13 19:53 ` Vince Weaver
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=f2c6502a-f13e-a663-f1f5-c441964d77ac@intel.com \
--to=dave.hansen@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rodrigo.vivi@intel.com \
--cc=vincent.weaver@maine.edu \
/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).