mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Alexander Sergeyev <sergeev917@gmail.com>
Cc: Mario.Limonciello@dell.com, dvhart@infradead.org,
	andy@infradead.org, linux-kernel@vger.kernel.org,
	mjg59@srcf.ucam.org, platform-driver-x86@vger.kernel.org
Subject: Re: PROBLEM: NULL pointer dereference in dell_set_arguments() in 4.15
Date: Sun, 4 Feb 2018 13:15:30 +0100	[thread overview]
Message-ID: <20180204121530.sl3h77mxbwusp2ul@pali> (raw)
In-Reply-To: <20180204092333.GA2010@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]

On Sunday 04 February 2018 12:23:33 Alexander Sergeyev wrote:
> Mario,
> 
> > Would you please try https://patchwork.kernel.org/patch/10194287/
> > And see if it cleans up this null pointer dereference?
> 
> Yes, it does.

So problem which I spotted is not only theoretical, but already affects
users... Pity that I have not looked at that patch which introduced that
problem deeply earlier :-(

So there is race condition between initializing dell-laptop driver and
calling exported function from this driver. But does not we still have
same problem at layer between dell-laptop.ko dell-sbios.ko and
dell-smbios-*.ko?

To make dell_micmute_led_set() work properly we need to ensure that
either WMI or SMM driver is already loaded and initialized.

> 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.

It should go in next round of merging into linus tree and after that
with proper commit message tags it should included in next stable
versions.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2018-02-04 12:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03 16:20 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
2018-02-04 12:15     ` Pali Rohár [this message]
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=20180204121530.sl3h77mxbwusp2ul@pali \
    --to=pali.rohar@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=platform-driver-x86@vger.kernel.org \
    --cc=sergeev917@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

all inboxes | Powered by JetHome®