LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: "Haar János" <djani22@netcenter.hu> To: "David Chinner" <dgc@sgi.com> Cc: <dgc@sgi.com>, <linux-xfs@oss.sgi.com>, <linux-kernel@vger.kernel.org> Subject: Re: xfslogd-spinlock bug? Date: Tue, 19 Dec 2006 00:39:46 +0100 [thread overview] Message-ID: <001a01c722fd$df5ca710$0400a8c0@dcccs> (raw) In-Reply-To: 20061218223637.GP44411608@melbourne.sgi.com ----- Original Message ----- 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> Sent: Monday, December 18, 2006 11:36 PM Subject: Re: xfslogd-spinlock bug? > On Mon, Dec 18, 2006 at 09:17:50AM +0100, Haar János wrote: > > From: "David Chinner" <dgc@sgi.com> > > > > The NBD serves through eth1, and it is on the CPU3, but the ide0 is on > > the > > > > CPU0. > > > > > > I'd say your NBD based XFS filesystem is having trouble. > > > > > > > > Are you using XFS on a NBD? > > > > > > > > Yes, on the 3. source. > > > > > > 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? > > > > > > > Dec 16 12:08:36 dy-base RSP: 0018:ffff81011fdedbc0 EFLAGS: 00010002 > > > > > > Dec 16 12:08:36 dy-base RAX: 0000000000000033 RBX: 6b6b6b6b6b6b6b6b > > RCX: > > > > > ^^^^^^^^^^^^^^^^ > > > > > Anyone recognise that pattern? > > 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? > > 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? Thanks, Janos > > Cheers, > > Dave. > -- > Dave Chinner > Principal Engineer > SGI Australian Software Group
next prev parent reply other threads:[~2006-12-18 23:41 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 [this message] 2006-12-19 2:52 ` David Chinner 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='001a01c722fd$df5ca710$0400a8c0@dcccs' \ --to=djani22@netcenter.hu \ --cc=dgc@sgi.com \ --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).