mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Jan Kara <jack@suse.cz>
Cc: Nick Piggin <npiggin@suse.de>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: unmount oops in log_do_checkpoint
Date: Wed, 18 Jan 2006 06:41:37 +0100	[thread overview]
Message-ID: <20060118054136.GA27838@wotan.suse.de> (raw)
In-Reply-To: <20060117222353.GA26770@atrey.karlin.mff.cuni.cz>

[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]

On Tue, Jan 17, 2006 at 11:23:53PM +0100, Jan Kara wrote:
> > On Tue, Jan 17, 2006 at 05:32:35PM +0100, Jan Kara wrote:
> > > > On Tue, Jan 17, 2006 at 12:59:45PM +0100, Nick Piggin wrote:
> > > > 
> > > > Maybe it is because people haven't been turning on their debugging options,
> > > > tsk tsk ;) It only oopses when DEBUG_SLAB and DEBUG_PAGEALLOC are both
> > > > enabled. And only then when the jbd patch is not reverted. Weird.
> > >   Hmm, that's really strange, maybe we have some use-after-free
> > > problem or so... I'll see what I can do :).
> > > 
> > 
> > Are you able to reproduce? If not I can test patches...
>   Hmm, I was not able to reproduce the problem even with those debug
> options set :(. As I'm looking into the code it seems that somebody
> managed to free the transaction but did not clear the
> j_checkpoint_transactions pointer. It's even stranger that it's during
> umount time when there should not be much processes playing with the JBD
> structures on that filesystem.
>   Attached is the patch that fixes two minor possible problems I've
> found. Neither of them should be causing your oops but one never knows
> :). Also turn on the JBD debugging in config. Maybe it spits something
> useful. If you still see the same oops, I'll create some debugging
> patch.

This patch does the trick. Survived several reboots now while without
the patch it has oopsed 100% of the time so far. Thanks!

I have also attached a full jbd debug output and oops for the vanilla
2.6.16-rc1 case, just in case that helps.

>   BTW: the oops during umount is after some activity on the filesystem
> or you just mount & umount?
> 

mount,unmount doesn't seem to trigger it, nor does a bit of filesystem
activity. I haven't tracked down exactly what *does* trigger it, but
booting then rebooting does it every time.

Nick

[-- Attachment #2: dmesg.bad.gz --]
[-- Type: application/x-gunzip, Size: 4380 bytes --]

  reply	other threads:[~2006-01-18  5:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16 16:04 Nick Piggin
2006-01-16 21:22 ` Jan Kara
2006-01-17 11:37   ` Nick Piggin
2006-01-17 11:46     ` Andrew Morton
2006-01-17 11:59       ` Nick Piggin
2006-01-17 14:09         ` Nick Piggin
2006-01-17 16:32           ` Jan Kara
2006-01-17 16:36             ` Nick Piggin
2006-01-17 22:23               ` Jan Kara
2006-01-18  5:41                 ` Nick Piggin [this message]
2006-01-18 10:35                   ` Jan Kara

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=20060118054136.GA27838@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=akpm@osdl.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®