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 116471] Core in ext4 filesystem on a Dell Server
Date: Fri, 15 Apr 2016 21:48:14 +0000	[thread overview]
Message-ID: <bug-116471-13602-J41892DPVB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-116471-13602@https.bugzilla.kernel.org/>

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

Eric Sandeen <sandeen@redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sandeen@redhat.com

--- Comment #1 from Eric Sandeen <sandeen@redhat.com> ---
First of all, this looks like a rebuilt centos kernel based on RHEL7.0 - i.e a
modified, old, distro kernel.  So upstream bugzilla may not be the best place
for it.

That said, this is down a do_coredump() path, hitting BUG_ON(irqs_disabled())

We've seen similar things on xfs, also down the do_coredump() path, in an
upstream 3.14 kernel (http://oss.sgi.com/archives/xfs/2014-02/msg00325.html).

That launched a long thread, and nobody seemed to come to an answer of why
interrupts were disabled at that point.

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

  reply	other threads:[~2016-04-15 21:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 21:00 [Bug 116471] New: Core in ext4 filesystem on a Dell Server bugzilla-daemon
2016-04-15 21:48 ` bugzilla-daemon [this message]
2016-04-16  2:31 ` [Bug 116471] " bugzilla-daemon
2016-04-16  5:21 ` 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-116471-13602-J41892DPVB@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).