netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 205621] New: Linux next-20191121 NULL dereference on start-up, leading to unusable system
Date: Thu, 21 Nov 2019 08:36:07 -0800	[thread overview]
Message-ID: <20191121083607.09dafe7d@hermes.lan> (raw)



Begin forwarded message:

Date: Thu, 21 Nov 2019 14:48:31 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 205621] New: Linux next-20191121 NULL dereference on start-up, leading to unusable system


https://bugzilla.kernel.org/show_bug.cgi?id=205621

            Bug ID: 205621
           Summary: Linux next-20191121 NULL dereference on start-up,
                    leading to unusable system
           Product: Networking
           Version: 2.5
    Kernel Version: next-20191121
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: nicholas.johnson-opensource@outlook.com.au
        Regression: No

Created attachment 286005
  --> https://bugzilla.kernel.org/attachment.cgi?id=286005&action=edit  
The .config

Linux next-20191121 - .config file attached.

NULL dereference on start-up, leading to unusable system.

Used "git clone --depth=1 --single-branch --branch next-20191115
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git"

Where I am, I cannot use serial console to save the stack trace.

I will attach a photo of the screen.

The top few functions are:

kernfs_find_and_get_ns
sysfs_remove_group
netdev_queue_update_kobjects
netdev_unregister_kobject

This leads me to believe that it is part of networking.

I will do a bisect if I have to, but given how time consuming they are on a
quad-core machine, I hope somebody else with a 32-core Threadripper can step up
to the task.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2019-11-21 16:36 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=20191121083607.09dafe7d@hermes.lan \
    --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).