linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 51391] BUG: unable to handle kernel NULL pointer dereference
Date: Fri,  7 Dec 2012 20:13:06 +0000 (UTC)	[thread overview]
Message-ID: <20121207201306.50D2911FE9C@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-51391-13602@https.bugzilla.kernel.org/>

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


Theodore Tso <tytso@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |REJECTED
         Resolution|                            |UNREPRODUCIBLE




--- Comment #8 from Theodore Tso <tytso@mit.edu>  2012-12-07 20:13:05 ---
Can you replicate the problem **without** using Spruce?

In any case, I would suggest sending a bug report with Canonical, since this is
a Ubuntu kernel --- and despite my best efforts, I can not replicate the
problem as you have described it on a stock 3.2.29 or 3.7-rc4 development
kernel.

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

  parent reply	other threads:[~2012-12-07 20:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 11:21 [Bug 51391] New: BUG: unable to handle kernel NULL pointer dereference bugzilla-daemon
2012-12-07 16:15 ` [Bug 51391] " 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 [this message]
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=20121207201306.50D2911FE9C@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 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).