From: Zoltan Kiss <zoltan.kiss@citrix.com>
To: James Dingwall <james-xen@dingwall.me.uk>, xen-devel@lists.xen.org
Subject: Re: netback oops in Linux 3.14 / 3.15
Date: Tue, 10 Jun 2014 19:42:57 +0100 [thread overview]
Message-ID: <539751B1.2040602@citrix.com> (raw)
In-Reply-To: <20140610182055.GA7348@dingwall.me.uk>
Hi,
It is very likely to be a recent issue, please apply this fix onto your
kernel:
http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/drivers/net/xen-netback?id=59ae9fc67007da8b5aea7b0a31c3607745cfbfee
Zoli
On 10/06/14 19:20, James Dingwall wrote:
> Hi,
>
> Under Linux 3.14.6 and 3.15 I am getting a BUG_ON() from netback in xenvif_rx_action(). Under 3.15 it is the line at
> 629 which is triggering:
>
> BUG_ON(ring_slots_used > max_slots_needed);
>
> The conditions are a 3.15.0 dom0 with Xen 4.4.0, a guest domain running the same 3.15.0 kernel, an rsync in the guest
> where the source filesystem is NFS mounted from the dom0.
>
> I have added a printk to log the values which is seen as the first line in the attached trace. Is there an off-by-one
> error in the calculation for max_slots_needed or is it worth adding some more printks to find out how the value was
> calculated?
>
> Please let me know if any other information about my configuration is required.
>
> Thanks,
> James
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2014-06-10 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 18:20 netback oops in Linux 3.14 / 3.15 James Dingwall
2014-06-10 18:42 ` Zoltan Kiss [this message]
2014-06-10 19:51 ` James Dingwall
2014-08-19 9:30 ` Dennis Lan (dlan)
2014-08-19 19:26 ` Zoltan Kiss
2014-09-19 8:44 ` Dennis Lan (dlan)
2014-09-19 12:37 ` Wei Liu
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=539751B1.2040602@citrix.com \
--to=zoltan.kiss@citrix.com \
--cc=james-xen@dingwall.me.uk \
--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.