All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 216953] New: BUG: kernel NULL pointer dereference, address: 0000000000000008
Date: Thu, 19 Jan 2023 18:25:43 +0000	[thread overview]
Message-ID: <bug-216953-13602@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 216953
           Summary: BUG: kernel NULL pointer dereference, address:
                    0000000000000008
           Product: File System
           Version: 2.5
    Kernel Version: 6.1.7
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: gjunk2@sapience.com
        Regression: No

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

System has RAID6 with ext4 filesystem - 6 x 8TB drives.

Attached are config used to build kernel, output of ver_linux, the raw journal
as well as same run through scripts/decode_stacktrace.sh.

Note that while selinux is in kernel, there it is not being used.

thanks.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2023-01-20  5:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 18:25 bugzilla-daemon [this message]
2023-01-19 18:26 ` [Bug 216953] BUG: kernel NULL pointer dereference, address: 0000000000000008 bugzilla-daemon
2023-01-19 18:26 ` bugzilla-daemon
2023-01-19 18:26 ` bugzilla-daemon
2023-01-19 18:32 ` bugzilla-daemon
2023-01-19 18:45 ` bugzilla-daemon
2023-01-19 20:21 ` bugzilla-daemon
2023-01-19 20:36 ` bugzilla-daemon
2023-01-22 11:23 ` bugzilla-daemon

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=bug-216953-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-ext4@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.