From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: William Dauchy <wdauchy@gmail.com>, shli@fusionio.com
Cc: stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
xen-devel@lists.xensource.com, Shaohua Li <shli@kernel.org>,
linux-kernel@vger.kernel.org, Ben Hutchings <ben@decadent.org.uk>
Subject: Re: [Xen-devel] swap: don't do discard if no discard option added
Date: Mon, 21 May 2012 14:15:58 -0400 [thread overview]
Message-ID: <20120521181558.GA7829@phenom.dumpdata.com> (raw)
In-Reply-To: <CAJ75kXbC3gqQAaghKo2i1L650dw9-vrFuEwoy4defagoyR8p4Q@mail.gmail.com>
On Mon, May 21, 2012 at 12:30:45AM +0200, William Dauchy wrote:
> Hello,
>
> On Xen, when booting a guest with a system disk and an additional swap
> disk I'm getting a calltrace.
> xen hypervisor: 4.1.2; linux dom0: v3.3.6; linux guest: v3.2.17
> When booting without a swap disk, I don't have the issue.
> I also tested a guest with v3.3.6: same problem. But from v3.4-rc2,
> the issue is fixed.
> I cherry-picked:
> 052b198 swap: don't do discard if no discard option added
So you are asking for 052b198 to be back-ported.
I am OK with that but I think Shaohua needs to Ack that and
ask Greg to put it on stable@kernel.org
> Applied and tested on top of v3.2.17 and v3.3.6, it fixes the issue.
>
> Pid: 0, comm: swapper/0 Not tainted 3.2.17-x86_64 #12
> Call Trace:
> <IRQ>
> [<ffffffff810919da>] ? handle_irq_event_percpu+0x3a/0x140
> [<ffffffff81091b29>] ? handle_irq_event+0x49/0x80
> [<ffffffff81094e7d>] ? handle_edge_irq+0x6d/0x120
> [<ffffffff81229088>] ? __xen_evtchn_do_upcall+0x1b8/0x280
> [<ffffffff8122a442>] ? xen_evtchn_do_upcall+0x22/0x40
> [<ffffffff8133f4fe>] ? xen_do_hypervisor_callback+0x1e/0x30
> <EOI>
> [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
> [<ffffffff810013aa>] ? hypercall_page+0x3aa/0x1000
> [<ffffffff8100768c>] ? xen_safe_halt+0xc/0x20
> [<ffffffff81013563>] ? default_idle+0x23/0x40
> [<ffffffff8100b073>] ? cpu_idle+0x63/0xb0
> [<ffffffff81654c43>] ? start_kernel+0x362/0x36d
> [<ffffffff81657491>] ? xen_start_kernel+0x558/0x55e
> Code: 39 ed 0f 84 1c 02 00 00 44 8b 7b 48 4c 8b 73 50 41 83 ef 01 41
> 21 ef 49 6b c7 70 4d 8b 64 06 40 49 69 c4 d0 00 00 00 48 8d 14 03 <48>
> 8b 8a 78 02 00 00 48 89 4c 24 10 80 ba 09 02 00 00 00 74 6d
> RIP [<ffffffff8125ed66>] blkif_interrupt+0x66/0x320
> RSP <ffff88001fc03e18>
> ---[ end trace dfd4e5623eb06620 ]---
>
> Regards,
> --
> William
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-05-21 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 22:30 swap: don't do discard if no discard option added William Dauchy
2012-05-21 18:15 ` Konrad Rzeszutek Wilk [this message]
2012-05-21 21:02 ` [Xen-devel] " William Dauchy
2012-05-24 18:50 ` Greg Kroah-Hartman
2012-05-25 21:19 ` William Dauchy
2012-05-26 15:30 ` Ben Hutchings
2012-05-26 18:29 ` Hugh Dickins
2012-05-29 14:47 ` Konrad Rzeszutek Wilk
2012-05-30 20:29 ` William Dauchy
2012-05-30 21:16 ` Konrad Rzeszutek Wilk
2012-05-30 21:33 ` William Dauchy
2012-05-31 23:04 ` Hugh Dickins
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=20120521181558.GA7829@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=ben@decadent.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shli@fusionio.com \
--cc=shli@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wdauchy@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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.