From: Alexander Sergeyev <sergeev917@gmail.com>
To: Mario.Limonciello@dell.com
Cc: dvhart@infradead.org, andy@infradead.org,
linux-kernel@vger.kernel.org, mjg59@srcf.ucam.org,
pali.rohar@gmail.com, platform-driver-x86@vger.kernel.org
Subject: Re: PROBLEM: NULL pointer dereference in dell_set_arguments() in 4.15
Date: Sun, 4 Feb 2018 12:23:33 +0300 [thread overview]
Message-ID: <20180204092333.GA2010@localhost.localdomain> (raw)
In-Reply-To: <e489f5ee-34e5-4777-afe7-38d31d2ad3fd@Dell.com>
Mario,
>Would you please try https://patchwork.kernel.org/patch/10194287/
>And see if it cleans up this null pointer dereference?
Yes, it does.
Is there any estimates on when the patch will be merged into mainline? I want
to put something into my distribution bug tracker, but it's unlikely they will
use this patch before its stabilization.
>As for your suspend problem did you pick up the new firmware that contained
>the microcode update for Spectre? Or a microcode update from your
>distribution?
Yes, around a month ago (the firmware option). Still, there is a time frame
between the firmware update and the problem surfacing. As I said it was
eliminated by switching POST/fastboot to the thorough mode. I just have tried
to reproduce the problem with previous settings, but with no success. So, that
is (in a way) closed, but I have no idea what it was about.
Thank you.
next prev parent reply other threads:[~2018-02-04 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 16:20 PROBLEM: NULL pointer dereference in dell_set_arguments() in 4.15 Alexander Sergeyev
2018-02-03 20:22 ` Alexander Sergeyev
[not found] ` <e489f5ee-34e5-4777-afe7-38d31d2ad3fd@Dell.com>
2018-02-04 9:23 ` Alexander Sergeyev [this message]
2018-02-04 12:15 ` Pali Rohár
2018-02-04 14:25 ` Andy Shevchenko
2018-02-04 16:29 ` Alexander Sergeyev
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=20180204092333.GA2010@localhost.localdomain \
--to=sergeev917@gmail.com \
--cc=Mario.Limonciello@dell.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@vger.kernel.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