All of lore.kernel.org
 help / color / mirror / Atom feed
From: Atom2 <ariel.atom2@web2web.at>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>,
	"zoltan.kiss@citrix.com" <zoltan.kiss@citrix.com>
Subject: Re: kernel BUG at drivers/net/xen-netback/netback.c:540!
Date: Thu, 12 Jun 2014 19:13:30 +0200	[thread overview]
Message-ID: <5399DFBA.8020305@web2web.at> (raw)
In-Reply-To: <1402562478.4342.13.camel@kazak.uk.xensource.com>

Am 12.06.14 10:41, schrieb Ian Campbell:
> On Thu, 2014-06-12 at 01:05 +0200, Atom2 wrote:
>> Hi guys,
>> I just updated my kernel version for dom0 from 3.13.10 to 3.14.5 (both
>> gentoo hardened sources) when one of my virtual machines still running
>> on 3.13.10 suddenly froze. At that time I was about to update the kernel
>> for my domU when it froze. My XEN version is 4.3.2.
>
> Looks to be the same as
> http://lists.xen.org/archives/html/xen-devel/2014-06/msg01307.html
> for which Zoltan referred to:
> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/drivers/net/xen-netback?id=59ae9fc67007da8b5aea7b0a31c3607745cfbfee
>
Thanks Ian for your quick reply. The issue does indeed look similar on 
the face of it (alos given that I also do use an NFS mounted filesystem 
that was accessed at the time the problem occured). Unfortunately the 
patch seems to be for 3.15 only as it does not apply to my 3.14.5 
kernel. The error messages read as follows:

patching file drivers/net/xen-netback/netback.c
Hunk #1 succeeded at 164 (offset 1 line).
Hunk #2 succeeded at 177 (offset 1 line).
Hunk #3 succeeded at 188 (offset 1 line).
Hunk #4 succeeded at 197 (offset 1 line).
Hunk #5 succeeded at 233 (offset 1 line).
Hunk #6 succeeded at 272 (offset -1 lines).
Hunk #7 FAILED at 556.
Hunk #8 succeeded at 526 (offset -91 lines).
1 out of 8 hunks FAILED -- saving rejects to file 
drivers/net/xen-netback/netback.c.rej

Hunk #7 refers to the following piece of code in the patch:
@@ -541,12 +556,6 @@ static void xenvif_add_frag_responses(struct xenvif 
*vif, int status,
         }
  }

-struct xenvif_rx_cb {
-       int meta_slots_used;
-};
-
-#define XENVIF_RX_CB(skb) ((struct xenvif_rx_cb *)(skb)->cb)
-
  void xenvif_kick_thread(struct xenvif *vif)
  {
         wake_up(&vif->wq);


Now in my kernel sources after the function xenvif_add_frag_responses 
referred to by the patch there's neither a definition of a
struct xenvif_rx_cb { ...
nor a line reading
#define XENVIF_RX_CB ...
(both of which the patch tries to remove)

but rather the definition of a
struct skb_cb_overlay {
	int meta_slots_used;
};
(which obviously the patch does not expect to see there)

I guess I'd therefore need a slightly modified patch for the 3.14.5 
kernel sources to make it compile.

Many thanks in advance,
Atom2

      reply	other threads:[~2014-06-12 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 23:05 kernel BUG at drivers/net/xen-netback/netback.c:540! Atom2
2014-06-12  8:41 ` Ian Campbell
2014-06-12 17:13   ` Atom2 [this message]

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=5399DFBA.8020305@web2web.at \
    --to=ariel.atom2@web2web.at \
    --cc=Ian.Campbell@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=zoltan.kiss@citrix.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.