Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933563AbbLBRgi (ORCPT ); Wed, 2 Dec 2015 12:36:38 -0500 Received: from arcturus.aphlor.org ([188.246.204.175]:51220 "EHLO arcturus.aphlor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933280AbbLBRgV (ORCPT ); Wed, 2 Dec 2015 12:36:21 -0500 Date: Wed, 2 Dec 2015 12:36:09 -0500 From: Dave Jones To: Chris Mason , Josef Bacik , Linux Kernel , "J. Bruce Fields" , Jeff Layton , David Sterba Subject: Re: 4.4rc3 nfsd/btrfs kasan warning. Message-ID: <20151202173609.GA10996@codemonkey.org.uk> Mail-Followup-To: Dave Jones , Chris Mason , Josef Bacik , Linux Kernel , "J. Bruce Fields" , Jeff Layton , David Sterba References: <20151202145907.GA9425@codemonkey.org.uk> <565F0A20.40200@fb.com> <20151202160942.GA16348@codemonkey.org.uk> <20151202171320.GE8918@ret.masoncoding.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151202171320.GE8918@ret.masoncoding.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Score: -2.9 (--) X-Spam-Report: Spam report generated by SpamAssassin on "arcturus.aphlor.org" Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1200 Lines: 30 On Wed, Dec 02, 2015 at 12:14:56PM -0500, Chris Mason wrote: > On Wed, Dec 02, 2015 at 11:09:43AM -0500, Dave Jones wrote: > > On Wed, Dec 02, 2015 at 10:11:28AM -0500, Josef Bacik wrote: > > > On 12/02/2015 09:59 AM, Dave Jones wrote: > > > > Got a few of these in the logs this morning after an overnight rsync over nfs > > > > to an exported btrfs volume. > > > > > > That's probably us and not NFS, what line is that in > > > setup_cluster_bitmap? Thanks, > > > > If my math is correct, it's this.. > > > > if (entry->offset != bitmap_offset) > > > > I don't seem to be able to trigger it on demand unfortunatly. > > Is it possible we're blowing the stack? It seems pretty tricky to get a > stack out of bounds out of this code without flat out blowing through > it. Hm, there is a lot of debug crap on the stack from lockdep etc, though I didn't get any warnings from the other stack overflow checks. Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/