From: Borislav Petkov <bp@alien8.de>
To: Jiri Slaby <jslaby@suse.cz>
Cc: linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Michael Galbraith <mgalbraith@suse.de>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 00000000000001e0
Date: Mon, 24 Oct 2016 20:56:59 +0200 [thread overview]
Message-ID: <20161024185659.uwdkz23sic65eroc@pd.tnic> (raw)
In-Reply-To: <49489eb2-c7f5-369b-4552-d888cbc27719@suse.cz>
On Mon, Oct 24, 2016 at 05:28:24PM +0200, Jiri Slaby wrote:
> From the quick look, uart_write_wakeup should now be using refcounting.
> Does this help (compile-tested only)?
Yes, it does. Thanks!
Reported-and-tested-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-10-24 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 14:48 BUG: unable to handle kernel NULL pointer dereference at 00000000000001e0 Borislav Petkov
2016-10-24 15:19 ` Mike Galbraith
2016-10-24 15:28 ` Jiri Slaby
2016-10-24 18:56 ` Borislav Petkov [this message]
2016-10-25 1:47 ` Mike Galbraith
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=20161024185659.uwdkz23sic65eroc@pd.tnic \
--to=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mgalbraith@suse.de \
/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).