From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: liuxiaolei1124 <liuxiaolei1124@163.com>, xen-devel@lists.xensource.com
Subject: Re: about the patch: persistent grant maps for xen blk drivers
Date: Mon, 15 Oct 2012 09:19:30 -0400 [thread overview]
Message-ID: <20121015131930.GC4000@phenom.dumpdata.com> (raw)
In-Reply-To: <6f0a356f.934c.13a62ccac9a.Coremail.liuxiaolei1124@163.com>
On Mon, Oct 15, 2012 at 01:01:51PM +0800, liuxiaolei1124 wrote:
> Dear konrad:
> i have seen you put the patch "persisten grant maps for xen blk drivers" into you kernel, then dom0 crash .(https://lkml.org/lkml/2012/9/21/388 )my dom0 kernel is 2.6.32.36-0.5, and i put this patch in my kernel, there is a bug too, and the stack is much like yours. And i found a strange phenomenon. when i add a printk log such as "printk ("enter func") " in blkif_completion or other function in xen-blkfront.c, guest run well. But after i remove this printk log, guest crash when i start.
Hey. Roger posted a follow up patch that has this fixed. You should
look at that.
Also CC-ing xen-devel here.
> and the crash stack is :
> blkif_int -> blkif_completion
> guest page fault in
>
> + if (bret->operation == BLKIF_OP_READ)
> + rq_for_each_segment(bvec, s->request, iter) {
> + shared_data = kmap_atomic
> + (pfn_to_page(s->grants_used[i++]->frame)); // page fault
> + bvec_data = bvec_kmap_irq(bvec, &flags);
> + memcpy(bvec_data, shared_data + bvec->bv_offset,
> + bvec->bv_len);
> + bvec_kunmap_irq(bvec_data, &flags);
> + kunmap_atomic(shared_data);
> + }
>
> in kernel 2.6.32.36-0.5, my patch is :
>
> + if (bret->operation == BLKIF_OP_READ)
> + rq_for_each_segment(bvec, s->request, iter) {
> + shared_data = kmap_atomic
> + (pfn_to_page(s->grants_used[i++]->frame), KM_USER0);
> + bvec_data = bvec_kmap_irq(bvec, &flags);
> + memcpy(bvec_data, shared_data + bvec->bv_offset,
> + bvec->bv_len);
> + bvec_kunmap_irq(bvec_data, &flags);
> + kunmap_atomic(shared_data, KM_USER0);
> + }
>
> I don't know what's wrong? mybe function kmap_atomic in my patch is incorrect. I look forward toyour reply, thank you.
>
> Best wishes.
> eric.liu
>
>
>
>
>
>
>
>
>
>
>
>
>
next parent reply other threads:[~2012-10-15 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6f0a356f.934c.13a62ccac9a.Coremail.liuxiaolei1124@163.com>
2012-10-15 13:19 ` Konrad Rzeszutek Wilk [this message]
2012-10-16 4:35 ` about the patch: persistent grant maps for xen blk drivers liuxiaolei1124
2012-10-17 18:28 ` Konrad Rzeszutek Wilk
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=20121015131930.GC4000@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=liuxiaolei1124@163.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 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).