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 31742] New: got a "kernel BUG at fs/dcache.c:440!"
Date: Wed, 23 Mar 2011 15:14:31 GMT	[thread overview]
Message-ID: <bug-31742-13602@https.bugzilla.kernel.org/> (raw)

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

           Summary: got a "kernel BUG at fs/dcache.c:440!"
           Product: File System
           Version: 2.5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: ruediger@blueboot.org
        Regression: No


While traversing /usr with a python script, i got a message saying "kernel
BUG". Its the first time i got something like this in the last 12 years using
linux, so i guessed, i should report it. The message is attached as a jpeg.

so long
Mathias

-- 
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:[~2011-03-23 15:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 15:14 bugzilla-daemon [this message]
2011-03-23 15:15 ` [Bug 31742] got a "kernel BUG at fs/dcache.c:440!" bugzilla-daemon
2011-03-23 15:18 ` bugzilla-daemon
2011-03-23 15:20 ` bugzilla-daemon
2011-03-23 15:21 ` bugzilla-daemon
2011-03-23 15:21 ` bugzilla-daemon
2011-03-23 15:23 ` bugzilla-daemon
2011-03-23 19:31 ` bugzilla-daemon
2011-03-23 23:45 ` bugzilla-daemon
2011-03-24  8:51 ` bugzilla-daemon
2012-08-20 15:14 ` 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-31742-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 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).