All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 210185] kernel BUG at fs/ext4/page-io.c:126!
Date: Fri, 13 Nov 2020 20:10:20 +0000	[thread overview]
Message-ID: <bug-210185-13602-ebKRR1LdC2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210185-13602@https.bugzilla.kernel.org/>

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

Amy (enbyamy@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |enbyamy@gmail.com

--- Comment #1 from Amy (enbyamy@gmail.com) ---
Hey there!

Traced back that file. That line runs page_buffers(), which launches a bug if
PagePrivate is false. 

#define page_buffers(page)                                      \
        ({                                                      \
                BUG_ON(!PagePrivate(page));                     \
                ((struct buffer_head *)page_private(page));     \
        })

What application were you running, if I may ask?

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

  reply	other threads:[~2020-11-13 20:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13  9:16 [Bug 210185] New: kernel BUG at fs/ext4/page-io.c:126! bugzilla-daemon
2020-11-13 20:10 ` bugzilla-daemon [this message]
2020-11-13 22:03 ` [Bug 210185] " bugzilla-daemon
2020-11-17 19:07 ` bugzilla-daemon
2020-11-18 10:30 ` bugzilla-daemon
2020-11-18 10:31 ` bugzilla-daemon
2020-11-18 10:33 ` bugzilla-daemon
2020-11-18 10:33 ` bugzilla-daemon
2020-11-18 13:09 ` bugzilla-daemon
2020-11-18 13:09 ` bugzilla-daemon
2020-11-20  7:49 ` bugzilla-daemon
2021-02-02 11:00 ` bugzilla-daemon
2021-02-02 16:23 ` bugzilla-daemon
2021-02-02 17:06 ` bugzilla-daemon
2021-02-03  8:19 ` bugzilla-daemon
2021-02-18 12:57 ` 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-210185-13602-ebKRR1LdC2@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.