All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	ian.jackson@eu.citrix.com, xen-devel <xen-devel@lists.xen.org>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: kernel BUG at drivers/xen/grant-table.c:923!
Date: Fri, 17 Apr 2015 11:47:01 +0100	[thread overview]
Message-ID: <1429267621.25195.265.camel@citrix.com> (raw)
In-Reply-To: <5530E118.5070702@citrix.com>

On Fri, 2015-04-17 at 11:31 +0100, David Vrabel wrote:
> On 17/04/15 11:28, Ian Campbell wrote:
> > (Was Re: [osstest test] 50423: regressions - FAIL)
> > 
> > This cropped up in an osstest flight (the results only go to Ian and I).
> > 
> > On Fri, 2015-04-17 at 11:10 +0100, Ian Campbell wrote:
> >> On Thu, 2015-04-16 at 21:36 +0000, osstest service user wrote:
> >>> flight 50423 osstest real [real]
> >>> http://logs.test-lab.xenproject.org/osstest/logs/50423/
> >>>
> >>> Regressions :-(
> >>>
> >>> Tests which did not succeed and are blocking,
> >>> including tests which could not be run:
> >>>  test-armhf-armhf-xl          15 guest-start/debian.repeat fail REGR. vs. 50331
> >>
> >>
> >> Looks to have been a real issue:
> >>
> >> http://logs.test-lab.xenproject.org/osstest/logs/50423/test-armhf-armhf-xl/serial-cubietruck-gleizes.log
> >> Apr 14 19:01:21.834851 [ 1229.470934] ------------[ cut here ]------------
> >> Apr 14 19:01:22.445308 [ 1229.471001] kernel BUG at drivers/xen/grant-table.c:923!
> > 
> > This seems familiar, anyone remember it? (CCing ARM, netback and generic
> > Linux maintainers).
> 
> This doesn't look familiar to me.  What BUG_ON() is this?

The one in gnttab_batch_copy:

        void gnttab_batch_copy(struct gnttab_copy *batch, unsigned count)
        {
                struct gnttab_copy *op;
        
                if (HYPERVISOR_grant_table_op(GNTTABOP_copy, batch, count))
                        BUG();
                for (op = batch; op < batch + count; op++)
                        if (op->status == GNTST_eagain)
                                gnttab_retry_eagain_gop(GNTTABOP_copy, op,
                                                        &op->status, __func__);
        }
        EXPORT_SYMBOL_GPL(gnttab_batch_copy);
        
The actual hypercall has failed, which is a pretty unusual failure case.
r0 == fffffff2 is likely the return code, which is -14 == EFAULT.

So I suppose something is up with the pointer at batch.

Ian.

  reply	other threads:[~2015-04-17 10:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <osstest-50423-mainreport@xen.org>
     [not found] ` <1429265400.25195.246.camel@citrix.com>
2015-04-17 10:18   ` [PATCH OSSTEST] sg-run-job: Repeat rumpuserxen-demo-xenstorels test 150 times Ian Campbell
2015-05-14 10:44     ` Ian Jackson
2015-04-17 10:28   ` kernel BUG at drivers/xen/grant-table.c:923! Ian Campbell
2015-04-17 10:31     ` David Vrabel
2015-04-17 10:47       ` Ian Campbell [this message]
2015-04-17 10:45     ` Wei Liu
2015-04-17 10:49       ` Ian Campbell

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=1429267621.25195.265.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@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.