From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zoltan Kiss Subject: Re: netback oops in Linux 3.14 / 3.15 Date: Tue, 19 Aug 2014 14:26:06 -0500 Message-ID: <53F3A4CE.1000706@schaman.hu> References: <20140610182055.GA7348@dingwall.me.uk> <539751B1.2040602@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Dennis Lan (dlan)" Cc: James Dingwall , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Yes, it does worth to backport if the patch referred in the commit message is there. Zoli On 19/08/14 04:30, Dennis Lan (dlan) wrote: > Hello zoli: > should we back port this to longterm maintain kernel? current the > most recent version is 3.14.17 > > Lan > > On Wed, Jun 11, 2014 at 2:42 AM, Zoltan Kiss wrote: >> 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 >>> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xen.org >> http://lists.xen.org/xen-devel