From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 218205] New: kernel 6.6.3 NULL pointer dereference send UDP
Date: Wed, 29 Nov 2023 06:57:33 -0800 [thread overview]
Message-ID: <20231129065733.6f14ac4f@hermes.local> (raw)
Begin forwarded message:
Date: Wed, 29 Nov 2023 09:10:57 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 218205] New: kernel 6.6.3 NULL pointer dereference send UDP
https://bugzilla.kernel.org/show_bug.cgi?id=218205
Bug ID: 218205
Summary: kernel 6.6.3 NULL pointer dereference send UDP
Product: Networking
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: IPV4
Assignee: stephen@networkplumber.org
Reporter: netolish@gmail.com
Regression: No
Created attachment 305506
--> https://bugzilla.kernel.org/attachment.cgi?id=305506&action=edit
NULL pointer error log
In new 6.6.3 kernel on Gentoo during start chronyd kernel NULL pointer message
is show and after a while system hangs-up with kernel panic. 6.6.2 version
works fine.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2023-11-29 14:57 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=20231129065733.6f14ac4f@hermes.local \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.