xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>,
	'Christoph Moench-Tegeder' <cmt@burggraben.net>
Cc: 'Michael Collins' <mike@ark-net.org>,
	'Juergen Gross' <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
	'Alex Braunegg' <alex.braunegg@gmail.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [BUG] kernel bug encountered at drivers/net/xen-netback/netback.c:430!
Date: Wed, 10 Jan 2018 13:58:33 +0000	[thread overview]
Message-ID: <6ca3b938cb2949fba04f7fc9ce89f5aa@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <1fa2f53623a946e2b4ee2fc0b3632360@AMSPEX02CL03.citrite.net>

> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xenproject.org] On Behalf
> Of Paul Durrant
> Sent: 10 January 2018 12:52
> To: 'Christoph Moench-Tegeder' <cmt@burggraben.net>
> Cc: 'Michael Collins' <mike@ark-net.org>; 'Juergen Gross'
> <jgross@suse.com>; Wei Liu <wei.liu2@citrix.com>; 'Alex Braunegg'
> <alex.braunegg@gmail.com>; xen-devel@lists.xenproject.org
> Subject: Re: [Xen-devel] [BUG] kernel bug encountered at drivers/net/xen-
> netback/netback.c:430!
> 
> I have tracked down the problem to multiple calls to the zerocopy callback for
> the same ubuf_info. I am not sure exactly which patch introduced the issue
> but my suspicion is that it was one of the the MSG_ZEROCOPY series (see
> https://marc.info/?l=linux-netdev&m=149807997726733&w=2).
> I have a candidate patch to netback to make use of the ubuf_info ref count
> to handle the multiple callbacks and that certainly fixes the issue for me. I'll
> post this shortly recommending a backport to stable.
> 

Actually no need... The underlying issue was really a bug and has been fixed in 4.14.11. See https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.14.13&id=17155ea827b2fd81330a442ed56d0edafd9969e1

  Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-01-10 13:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22  6:40 [BUG] kernel bug encountered at drivers/net/xen-netback/netback.c:430! Alex Braunegg
2017-12-22  6:47 ` Juergen Gross
2017-12-22 20:35   ` Alex Braunegg
2017-12-28 18:05     ` Michael Collins
2017-12-28 19:31       ` Alex Braunegg
2018-01-03 13:54         ` Paul Durrant
2018-01-03 18:43           ` Alex Braunegg
2018-01-03 20:33           ` Christoph Moench-Tegeder
2018-01-04 10:29             ` Paul Durrant
2018-01-07 22:19               ` 'Christoph Moench-Tegeder'
2018-01-08  9:35                 ` Paul Durrant
2018-01-09  9:44                   ` Paul Durrant
2018-01-10 12:52                     ` Paul Durrant
2018-01-10 13:58                       ` Paul Durrant [this message]
2018-01-10 17:53                         ` 'Christoph Moench-Tegeder'
2018-01-10 19:55                           ` Alex Braunegg
  -- strict thread matches above, loose matches on Subject: below --
2017-12-20 21:03 Alex Braunegg

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=6ca3b938cb2949fba04f7fc9ce89f5aa@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=alex.braunegg@gmail.com \
    --cc=cmt@burggraben.net \
    --cc=jgross@suse.com \
    --cc=mike@ark-net.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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 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).