From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Don't request a bug report for unsafe module parameters
Date: Tue, 08 May 2018 13:03:12 +0300 [thread overview]
Message-ID: <87h8ni5usf.fsf@intel.com> (raw)
In-Reply-To: <20180507194549.GY17530@intel.com>
On Mon, 07 May 2018, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Sun, May 06, 2018 at 07:31:47PM +0100, Chris Wilson wrote:
>> Unsafe module parameters are just that, unsafe. If the user is foolish
>> enough to try them and the kernel breaks, they get to keep both pieces.
>> Don't ask them to file a bug report if they broke it themselves.
>>
>> References: https://bugs.freedesktop.org/show_bug.cgi?id=106423
>> Fixes: d15d7538c6d2 ("drm/i915: Tune down init error message due to failure injection")
>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Imre Deak <imre.deak@intel.com>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> I believe there are cases where having the reports would be extremely useful,
> like on PSR case.
> But of course prioritized as "Lowest".
>
> Better than not having anything and suddenly, when we switch
> things on, we start having so many reports at once.
>
> So, probably a different message would be worth trying?
AFAICT this only gets used via i915_load_error() when driver load fails.
BR,
Jani.
>
>> ---
>> drivers/gpu/drm/i915/i915_drv.c | 8 +++++++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
>> index 9b782045ae17..9c449b8d8eab 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.c
>> +++ b/drivers/gpu/drm/i915/i915_drv.c
>> @@ -101,7 +101,13 @@ __i915_printk(struct drm_i915_private *dev_priv, const char *level,
>> __builtin_return_address(0), &vaf);
>>
>> if (is_error && !shown_bug_once) {
>> - dev_notice(kdev, "%s", FDO_BUG_MSG);
>> + /*
>> + * Ask the user to file a bug report for the error, except
>> + * if they may have caused the bug by fiddling with unsafe
>> + * module parameters.
>> + */
>> + if (!test_taint(TAINT_USER))
>> + dev_notice(kdev, "%s", FDO_BUG_MSG);
>> shown_bug_once = true;
>> }
>>
>> --
>> 2.17.0
>>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-05-08 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 18:31 [PATCH] drm/i915: Don't request a bug report for unsafe module parameters Chris Wilson
2018-05-06 18:55 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-05-06 19:41 ` ✓ Fi.CI.IGT: " Patchwork
2018-05-07 6:37 ` [PATCH] " Jani Nikula
2018-05-07 8:03 ` Joonas Lahtinen
2018-05-07 19:45 ` Rodrigo Vivi
2018-05-08 10:03 ` Jani Nikula [this message]
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=87h8ni5usf.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.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