From: Jonathan Woithe <jwoithe@just42.net>
To: Jiri Slaby <jslaby@suse.cz>
Cc: kernel@kempniu.pl, dvhart@infradead.org, andy@infradead.org,
platform-driver-x86@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: NULL pointer dereference in call_fext_func [fujitsu_laptop]
Date: Tue, 19 Sep 2017 17:40:38 +0930 [thread overview]
Message-ID: <20170919081038.GE10399@marvin.atrad.com.au> (raw)
In-Reply-To: <541b9a7a-2224-9b81-aef3-3f06491f91e3@suse.cz>
On Tue, Sep 19, 2017 at 09:56:47AM +0200, Jiri Slaby wrote:
> we have this report from 4.13.1:
> BUG: unable to handle kernel NULL pointer dereference at 00000004
> IP: call_fext_func.isra.3+0x82/0xf0 [fujitsu_laptop]
> *pdpt = 0000000035e79001 *pde = 0000000000000000
> :
> It looks like fext is NULL, but bl_update_status passes it down to
> call_fext_func which obviously blows up.
>
> This was originally reported here:
> https://bugzilla.suse.com/show_bug.cgi?id=1058814
Thanks for the report.
This issue is already being discussed. See the platform drivers thread
"[PATCH] platform/x86: fujitsu-laptop: Don't oops when FUJ02E3 is not
presnt".
> Any ideas?
Until the above post to platform drivers it was thought that all Fujitsu
laptops had FUJ02E3 since this was what was observed on all models we had
access to.
An interim patch is under consideration.
Regards
jonathan
prev parent reply other threads:[~2017-09-19 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 7:56 NULL pointer dereference in call_fext_func [fujitsu_laptop] Jiri Slaby
2017-09-19 8:07 ` Andy Shevchenko
2017-09-19 8:12 ` Jonathan Woithe
2017-09-27 7:07 ` Darren Hart
2017-09-19 8:10 ` Jonathan Woithe [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=20170919081038.GE10399@marvin.atrad.com.au \
--to=jwoithe@just42.net \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=jslaby@suse.cz \
--cc=kernel@kempniu.pl \
--cc=linux-kernel@vger.kernel.org \
--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