From: Jason Andryuk <jason.p.andryuk@aero.org>
To: xen-devel@lists.xen.org, roger.pau@citrix.com
Cc: david.vrabel@citrix.com
Subject: Missed Stable backport? maybe [PATCH v2 0/4] xen-blk: bug fixes
Date: Fri, 20 Jun 2014 10:32:17 -0400 [thread overview]
Message-ID: <53A445F1.9010204@aero.org> (raw)
Hi Roger,
I'm seeing a crash on shutdown in xen_blkbk_unmap on 3.12.22. kdb backtrace below. Could this be the shutdown race fixed by "[PATCH v2 3/4] xen-blkback: fix shutdown race"? That email does not provide the observed backtrace, so I cannot compare.
The cover letter for "[PATCH v2 0/4] xen-blk: bug fixes" <Message-Id: 1391509575-3949-1-git-send-email-roger.pau@citrix.com> mentions backport to stable. However, stable was not CC-ed and the patches seem to be missing from linux-stable. Was this just an oversight?
Regards,
Jason
[0]kdb> bt
Stack traceback for pid 6523
0xffff880010033b10 6523 6522 1 0 R 0xffff880010033fd0 *block
ffff88007c603ae8 000000000000e02b ffffffff8167bec7 ffff88007c603b50
ffff8800103fc030 ffffffff81009f40 ffff88007c603b10 ffffffff8101ba19
ffff88007c603b38 ffffffff810ea205 0000000000000001 ffff880010033b10
Call Trace:
<IRQ> [<ffffffff8167bec7>] ? xen_blkbk_unmap+0x247/0x2f0
[<ffffffff81009f40>] ? xen_clocksource_read+0x20/0x30
[<ffffffff8101ba19>] ? sched_clock+0x9/0x10
[<ffffffff810ea205>] ? sched_clock_cpu+0xb5/0x100
[<ffffffff81147cab>] ? rcu_irq_exit+0x4b/0x90
[<ffffffff810bbcee>] ? irq_exit+0x4e/0x90
[<ffffffff8154d295>] ? xen_evtchn_do_upcall+0x35/0x50
[<ffffffff81b6ad7e>] ? xen_do_hypervisor_callback+0x1e/0x30
[<ffffffff81b68eca>] ? error_exit+0x2a/0x60
[<ffffffff81b689fb>] ? retint_restore_args+0x5/0x6
[<ffffffff81470cd2>] ? strlcpy+0x42/0x60
[<ffffffff8112803c>] ? cgroup_path+0xbc/0xd0
[<ffffffff8167bfff>] ? __end_block_io_op+0x8f/0x190
[<ffffffff8167c116>] ? end_block_io_op+0x16/0x30
[<ffffffff8120e47d>] ? bio_endio+0x1d/0x30
[<ffffffff818d4ea5>] ? dec_pending+0x195/0x300
[<ffffffff818d531f>] ? clone_endio+0x6f/0xa0
[<ffffffff8120e47d>] ? bio_endio+0x1d/0x30
[<ffffffff8144a608>] ? blk_update_request+0xc8/0x410
[<ffffffff8144a96c>] ? blk_update_bidi_request+0x1c/0x80
[<ffffffff8144a9ef>] ? blk_end_bidi_request+0x1f/0x60
[<ffffffff8144aab0>] ? blk_end_request+0x10/0x20
[<ffffffff8168a5f1>] ? scsi_io_completion+0xf1/0x640
[<ffffffff81683250>] ? scsi_finish_command+0xb0/0x110
[<ffffffff8168a3fe>] ? scsi_softirq_done+0x12e/0x160
[<ffffffff81450543>] ? blk_done_softirq+0x83/0xa0
[<ffffffff810bba70>] ? __do_softirq+0x100/0x250
[<ffffffff81b6ad1c>] ? call_softirq+0x1c/0x30
[<ffffffff81015cb5>] ? do_softirq+0x55/0x90
[<ffffffff810bbd1d>] ? irq_exit+0x7d/0x90
[<ffffffff8154d295>] ? xen_evtchn_do_upcall+0x35/0x50
[<ffffffff81b6ad7e>] ? xen_do_hypervisor_callback+0x1e/0x30
<EOI> [<ffffffff8100122a>] ? xen_hypercall_xen_version+0xa/0x20
[<ffffffff8100122a>] ? xen_hypercall_xen_version+0xa/0x20
[<ffffffff81009f0d>] ? xen_force_evtchn_callback+0xd/0x10
[<ffffffff8100a792>] ? check_events+0x12/0x20
[<ffffffff8100a77f>] ? xen_restore_fl_direct_reloc+0x4/0x4
[<ffffffff810085c4>] ? __xen_pgd_pin+0x124/0x2b0
[<ffffffff81008772>] ? xen_dup_mmap+0x22/0x30
[<ffffffff810b46c5>] ? dup_mm+0x385/0x580
[<ffffffff810b552d>] ? copy_process.part.33+0xc3d/0x1450
[<ffffffff810b5ef5>] ? do_fork+0xd5/0x300
[<ffffffff810c5a82>] ? __set_task_blocked+0x32/0x70
[<ffffffff810b61a6>] ? SyS_clone+0x16/0x20
[<ffffffff81b697c9>] ? stub_clone+0x69/0x90
[<ffffffff81b69469>] ? system_call_fastpath+0x16/0x1b
next reply other threads:[~2014-06-20 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 14:32 Jason Andryuk [this message]
2014-06-20 15:12 ` Missed Stable backport? maybe [PATCH v2 0/4] xen-blk: bug fixes Roger Pau Monné
2014-06-20 16:34 ` Jason Andryuk
2014-06-23 14:29 ` Jason Andryuk
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=53A445F1.9010204@aero.org \
--to=jason.p.andryuk@aero.org \
--cc=david.vrabel@citrix.com \
--cc=roger.pau@citrix.com \
--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.