From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 198253] New: stopping htb results in null pointer dereference
Date: Mon, 25 Dec 2017 09:52:49 -0800 [thread overview]
Message-ID: <20171225095249.41f03044@xeon-e3> (raw)
Begin forwarded message:
Date: Mon, 25 Dec 2017 08:25:44 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 198253] New: stopping htb results in null pointer dereference
https://bugzilla.kernel.org/show_bug.cgi?id=198253
Bug ID: 198253
Summary: stopping htb results in null pointer dereference
Product: Networking
Version: 2.5
Kernel Version: 4.15
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: lorinc.czegledi@gmail.com
Regression: No
Created attachment 261323
--> https://bugzilla.kernel.org/attachment.cgi?id=261323&action=edit
BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
the latest kernel linux415-4.15.r17121 as built by the manjaro team, using
fireqos traffic shapeing frontend with attached config produces BUG: unable to
handle kernel NULL pointer dereference at 0000000000000018
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2017-12-25 17:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171225095249.41f03044@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).