From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
David Vrabel <david.vrabel@citrix.com>,
Theodore Ts'o <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] 3.19 + xen-devel: kernel BUG at fs/ext4/page-io.c:85!
Date: Thu, 12 Feb 2015 12:28:35 +0100 [thread overview]
Message-ID: <54DC8E63.6000500@citrix.com> (raw)
In-Reply-To: <1518867277.20150212095451@eikelenboom.it>
Hello,
El 12/02/15 a les 9.54, Sander Eikelenboom ha escrit:
> Hi,
>
> With a 3.19 kernel + xen-devel tree pulled on top i run into this splat below.
> It's on a Xen PV-guest running a postgres database and doing a pg_dump at that
> moment in time, after running for a while (within 2 days or so).
>
> --
> Sander
>
> [139595.736073] ------------[ cut here ]------------
> [139595.736073] kernel BUG at fs/ext4/page-io.c:85!
> [139595.736073] invalid opcode: 0000 [#1] SMP
> [139595.736073] Modules linked in:
> [139595.736073] CPU: 0 PID: 25632 Comm: pg_dump Not tainted 3.19.0-20150209-doflr-xendevel-edid+ #1
> [139595.736073] task: ffff8800f8fd10c0 ti: ffff88006bc70000 task.ti: ffff88006bc70000
> [139595.736073] RIP: e030:[<ffffffff8126826f>] [<ffffffff8126826f>] ext4_finish_bio+0x24f/0x260
> [139595.736073] RSP: e02b:ffff8800fac03bc8 EFLAGS: 00010046
> [139595.736073] RAX: 004000000002002c RBX: ffff880060fa6170 RCX: 0000000000000034
> [139595.736073] RDX: 0000000000000000 RSI: ffffea00014a77c0 RDI: ffff8800f9357300
> [139595.736073] RBP: ffff8800fac03c58 R08: 0000000000000009 R09: 0000000000016830
> [139595.736073] R10: ffff8800ff820680 R11: 0000000000000000 R12: 0000000000000000
> [139595.736073] R13: ffff88006bf111a0 R14: 0000000000000000 R15: ffffea0000cd1800
> [139595.736073] FS: 00007f623b3f7720(0000) GS:ffff8800fac00000(0000) knlGS:0000000000000000
> [139595.736073] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
> [139595.736073] CR2: ffffffffff600400 CR3: 0000000091907000 CR4: 0000000000000660
> [139595.736073] Stack:
> [139595.736073] ffff8800fac03be8 ffffffff81bc11c2 ffffffff83140070 ffff8800fac03cc6
> [139595.736073] ffff8800f9357300 00001000244d0001 004000000000002c 0000001700000000
> [139595.736073] 0000000000000000 0000000000000002 ffff8800fac03c98 ffffffff8110582d
> [139595.736073] Call Trace:
> [139595.736073] <IRQ>
> [139595.736073] [<ffffffff81bc11c2>] ? _raw_spin_unlock_irqrestore+0x52/0x90
> [139595.736073] [<ffffffff8110582d>] ? lock_acquire+0xed/0x110
> [139595.736073] [<ffffffff81268698>] ext4_end_bio+0x58/0x110
> [139595.736073] [<ffffffff8144dea3>] bio_endio+0x53/0x90
> [139595.736073] [<ffffffff81453850>] blk_update_request+0x80/0x300
> [139595.736073] [<ffffffff81453af2>] blk_update_bidi_request+0x22/0x90
> [139595.736073] [<ffffffff8145451b>] __blk_end_bidi_request+0x1b/0x40
> [139595.736073] [<ffffffff8145455a>] __blk_end_request_all+0x1a/0x30
> [139595.736073] [<ffffffff816e59d1>] blkif_interrupt+0x731/0x8c0
AFAICT the crash is due to the ext4 code not finding it's private data
embedded in the page. xen-blkfront doesn't use page->private at all, so
I'm not sure who is touching this. The only Xen specific code that
touches page->private is the p2m code. Was the domain
saved/restored/migrated?
Roger.
next prev parent reply other threads:[~2015-02-12 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 8:54 3.19 + xen-devel: kernel BUG at fs/ext4/page-io.c:85! Sander Eikelenboom
2015-02-12 11:28 ` Roger Pau Monné
2015-02-12 11:28 ` Roger Pau Monné [this message]
2015-02-12 11:58 ` Sander Eikelenboom
2015-02-12 11:58 ` [Xen-devel] " Sander Eikelenboom
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=54DC8E63.6000500@citrix.com \
--to=roger.pau@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=tytso@mit.edu \
--cc=xen-devel@lists.xen.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.