All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 51391] New: BUG: unable to handle kernel NULL pointer dereference
Date: Fri,  7 Dec 2012 11:21:01 +0000 (UTC)	[thread overview]
Message-ID: <bug-51391-13602@https.bugzilla.kernel.org/> (raw)

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

           Summary: BUG: unable to handle kernel NULL pointer dereference
           Product: File System
           Version: 2.5
    Kernel Version: 3.2.0-29-generic
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: ktsirunyan@gmail.com
        Regression: No


Architecture :  x86_64 emulated by VirtualBox version 4.1.2_Ubuntu r38459
Distributive :     Ubuntu 12.04
File System  :     Ext4
Detected by the Spruce System (http://linuxtesting.org/spruce)
Bug appears when trying to mount a device with MS_NODEV flag attempted.
See the kernel message attached below.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2012-12-07 11:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 11:21 bugzilla-daemon [this message]
2012-12-07 16:15 ` [Bug 51391] BUG: unable to handle kernel NULL pointer dereference bugzilla-daemon
2012-12-07 16:23 ` bugzilla-daemon
2012-12-07 16:25 ` bugzilla-daemon
2012-12-07 17:10 ` bugzilla-daemon
2012-12-07 17:12 ` bugzilla-daemon
2012-12-07 17:39 ` bugzilla-daemon
2012-12-07 18:04 ` bugzilla-daemon
2012-12-07 18:15 ` bugzilla-daemon
2012-12-07 20:13 ` bugzilla-daemon
2012-12-10  8:23 ` bugzilla-daemon
2013-02-11 10:04 ` 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-51391-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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.