LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com> To: "Haar János" <djani22@netcenter.hu> Cc: David Chinner <dgc@sgi.com>, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: xfslogd-spinlock bug? Date: Tue, 19 Dec 2006 13:52:29 +1100 [thread overview] Message-ID: <20061219025229.GT33919298@melbourne.sgi.com> (raw) In-Reply-To: <001a01c722fd$df5ca710$0400a8c0@dcccs> On Tue, Dec 19, 2006 at 12:39:46AM +0100, Haar János wrote: > From: "David Chinner" <dgc@sgi.com> > > On Mon, Dec 18, 2006 at 09:17:50AM +0100, Haar János wrote: > > > From: "David Chinner" <dgc@sgi.com> > > > > Ok, I've never heard of a problem like this before and you are doing > > > > something that very few ppl are doing (i.e. XFS on NBD). I'd start > > > > Hence I'd start by suspecting a bug in the NBD driver. > > > > > > Ok, if you have right, this also can be in context with the following > issue: > > > > > > http://download.netcenter.hu/bughunt/20061217/messages.txt (10KB) > > > > Which appears to be a crash in wake_up_process() when doing memory > > reclaim (waking the xfsbufd). > > Sorry, can you translate it to "poor mans language"? :-) > This is a different bug? Don't know - it's a different crash, but once again one that I've never heard of occurring before. > > Ok, I've found this pattern: > > > > #define POISON_FREE 0x6b > > > > Can you confirm that you are running with CONFIG_DEBUG_SLAB=y? > > Yes, i build with this option enabled. > Is this wrong? No, but it does slow your machine down. > > If so, we have a use after free occurring here and it would also > > explain why no-one has reported it before. > > > > FWIW, can you turn on CONFIG_XFS_DEBUG=y and see if that triggers > > a different bug check prior to the above dump? > > [root@X64 linux-2.6.19]# make bzImage > scripts/kconfig/conf -s arch/x86_64/Kconfig > .config:7:warning: trying to assign nonexistent symbol XFS_DEBUG > > I have missed something? No - I forgot that config option doesn't exist in mainline XFS - it's only in the dev tree. FWIW, I've run XFSQA twice now on a scsi disk with slab debuggin turned on and I haven't seen this problem. I'm not sure how to track down the source of the problem without a test case, but as a quick test, can you try the following patch? Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group --- fs/xfs/linux-2.6/xfs_buf.c | 4 ++++ 1 file changed, 4 insertions(+) Index: 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_buf.c =================================================================== --- 2.6.x-xfs-new.orig/fs/xfs/linux-2.6/xfs_buf.c 2006-12-19 12:22:54.000000000 +1100 +++ 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_buf.c 2006-12-19 13:48:36.937118569 +1100 @@ -942,11 +942,14 @@ xfs_buf_unlock( /* * Pinning Buffer Storage in Memory * Ensure that no attempt to force a buffer to disk will succeed. + * Hold the buffer so we don't attempt to free it while it + * is pinned. */ void xfs_buf_pin( xfs_buf_t *bp) { + xfs_buf_hold(bp); atomic_inc(&bp->b_pin_count); XB_TRACE(bp, "pin", (long)bp->b_pin_count.counter); } @@ -958,6 +961,7 @@ xfs_buf_unpin( if (atomic_dec_and_test(&bp->b_pin_count)) wake_up_all(&bp->b_waiters); XB_TRACE(bp, "unpin", (long)bp->b_pin_count.counter); + xfs_buf_rele(bp); } int
next prev parent reply other threads:[~2006-12-19 2:52 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-11 23:00 xfslogd-spinlock bug? Haar János 2006-12-12 14:32 ` Justin Piszcz 2006-12-13 1:11 ` Haar János 2006-12-16 11:19 ` Haar János 2006-12-17 22:44 ` David Chinner 2006-12-17 23:56 ` Haar János 2006-12-18 6:24 ` David Chinner 2006-12-18 8:17 ` Haar János 2006-12-18 22:36 ` David Chinner 2006-12-18 23:39 ` Haar János 2006-12-19 2:52 ` David Chinner [this message] 2006-12-19 4:47 ` David Chinner 2006-12-27 12:58 ` Haar János 2007-01-07 23:14 ` David Chinner 2007-01-10 17:18 ` Janos Haar 2007-01-11 3:34 ` David Chinner 2007-01-11 20:15 ` Janos Haar
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=20061219025229.GT33919298@melbourne.sgi.com \ --to=dgc@sgi.com \ --cc=djani22@netcenter.hu \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-xfs@oss.sgi.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: linkBe 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).