mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: jfs-discussion@lists.sourceforge.net,
	Johannes Weiner <hannes@saeurebad.de>,
	linux-kernel@vger.kernel.org
Subject: Re: latest -git: BUG at fs/jfs/namei.c:512 assert(ip->i_nlink)
Date: Fri, 18 Jul 2008 16:58:22 -0500	[thread overview]
Message-ID: <1216418302.30152.6.camel@norville.austin.ibm.com> (raw)
In-Reply-To: <19f34abd0807181108r53ea74adsd471e49f87d77024@mail.gmail.com>

On Fri, 2008-07-18 at 20:08 +0200, Vegard Nossum wrote:
> On Fri, Jul 18, 2008 at 7:29 PM, Dave Kleikamp
> <shaggy@linux.vnet.ibm.com> wrote:
> >
> > xtTruncate can call release_metapage() in several places.  If you still
> > have this kernel, could you please run addr2line against c02e4202?  If
> > you've rebuilt your kernel since then, I understand.
> 
> Sorry, it's gone. However, I just recompiled it and the size of the
> function is now 0x105f, and the offset 0xd42 matches with a call to
> release_metapage. So with this new address, it's this call:
> 
> $ addr2line -e vmlinux -i c02e428d
> fs/jfs/jfs_metapage.h:101
> fs/jfs/jfs_xtree.c:3723
> 
> ...which is this one:
> 
>     /* invalidate empty leaf page */
>     discard_metapage(mp);

Thanks.  This helps some, but I'm not sure why it should fail there.
Possibly a memory corruption problem caused by a bug in an earlier error
path.

> With your two patches applied, I now got this:
> 
> ERROR: (device loop0): remounting filesystem as read-only
> blkno = 200000687, nblocks = f
> ERROR: (device loop0): dbFree: block to be freed is outside the map
> BUG: unable to handle kernel paging request at 338f8038

I see I've got a few of these to track down.  I'm sure there are more
than a couple more bugs you will uncover.

> $ addr2line -e vmlinux -i c02ee352
> fs/jfs/jfs_dmap.c:2188
> 
> You can also have a copy of my scripts if you want to try to reproduce
> it locally. But I don't mind testing either :-)

Can you please send me a copy.  For some of these, I'd like to get a
repeatable test case, so I'm not debugging several problems at once.

Thanks,
Shaggy
-- 
David Kleikamp
IBM Linux Technology Center


  reply	other threads:[~2008-07-18 21:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 18:35 Vegard Nossum
2008-07-17 23:09 ` Dave Kleikamp
2008-07-18  8:10   ` Vegard Nossum
2008-07-18  8:29     ` Vegard Nossum
2008-07-18  8:43       ` Vegard Nossum
2008-07-18 17:29       ` Dave Kleikamp
2008-07-18 18:08         ` Vegard Nossum
2008-07-18 21:58           ` Dave Kleikamp [this message]
2008-07-22 16:30             ` Vegard Nossum
2008-07-18 17:15     ` Dave Kleikamp
2008-07-18 17:17       ` Vegard Nossum
2008-07-18 17:25         ` [Jfs-discussion] " Dave Kleikamp

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=1216418302.30152.6.camel@norville.austin.ibm.com \
    --to=shaggy@linux.vnet.ibm.com \
    --cc=hannes@saeurebad.de \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vegard.nossum@gmail.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: 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®