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 124651] ext4 bugon panic when I mmap a file
Date: Mon, 18 Jul 2016 13:25:14 +0000	[thread overview]
Message-ID: <bug-124651-13602-SsZT0jtSeZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-124651-13602@https.bugzilla.kernel.org/>

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

--- Comment #1 from Theodore Tso <tytso@mit.edu> ---
This is a Red Hat kernel, so ideally you should be reporting this to Red Hat.  
Because it's a Red Hat kernel, I can't easily determine what's on line 2263 of
fs/ext4/inode.c:

[55359.508185] kernel BUG at fs/ext4/inode.c:2263!

If you have access to Red Hat sources, can you give me an indication of what's
on that line?   One of the reasons why I ask is if I look at the upstream
sources, the only BUG_ON in mpage_prepare_extent_to_map is this one:

            wait_on_page_writeback(page);
            BUG_ON(PageWriteback(page));

And that's clearly a bug outside of ext4, because we've locked the page, so
once the page writeback flag is cleared, it shouldn't be set again.   So either
someone woke up the page without clearing the PageWriteback flag, or some other
racing process attempted to set the PageWriteback flag without holding the page
lock.

But this is assuming I'm looking at the correct BUG_ON --- and since this is a
Red Hat kernel, I can't be sure.

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

  reply	other threads:[~2016-07-18 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13  2:09 [Bug 124651] New: ext4 bugon panic when I mmap a file bugzilla-daemon
2016-07-18 13:25 ` bugzilla-daemon [this message]
2016-07-19  1:39 ` [Bug 124651] " bugzilla-daemon
2016-07-19  1:40 ` bugzilla-daemon
2016-07-19  1:40 ` 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-124651-13602-SsZT0jtSeZ@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).