linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Jan Kara <jack@suse.cz>, George Spelvin <linux@horizon.com>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Oops in ext3_block_to_path.isra.40+0x26/0x11b
Date: Fri, 16 Mar 2012 11:07:28 +0100	[thread overview]
Message-ID: <20120316100728.GA28098@quack.suse.cz> (raw)
In-Reply-To: <alpine.LNX.2.00.1203161028420.18356@pobox.suse.cz>

On Fri 16-03-12 10:29:56, Jiri Kosina wrote:
> On Fri, 16 Mar 2012, Jan Kara wrote:
> 
> > > CPU is a Core i3 530, on a Gigabyte motherbord, 4 GB RAM.  No ECC,
> > > unfortunately, so I can't rule out hardware bit rot.  Distribution is
> > > a fairly stock Debian/unstable.
> >   Hmm, is any mounting & unmounting happening during your backup? Because
> > the oops happened because sb->s_fs_info was NULL. Dissassembly shows:
> >   16:	48 8b 47 18          	mov    0x18(%rdi),%rax
> > store sb->s_blocksize into RAX
> >   1a:	48 8b 8f b0 02 00 00 	mov    0x2b0(%rdi),%rcx
> > store sb->s_fs_info into RCX
> >   21:	48 c1 e8 02          	shr    $0x2,%rax
> > This is division from EXT3_ADDR_PER_BLOCK() - RAX carries 1024 after
> > division so that looks correct.
> > 
> >   25:	48 85 db             	test   %rbx,%rbx
> > Now check passed i_block argument.
> > 
> >   28:	41 89 c4             	mov    %eax,%r12d
> >   2b:*	8b b1 94 00 00 00    	mov    0x94(%rcx),%esi     <-- trapping ins
> > Try to get RCX->s_addr_per_block_bits...
> > 
> >  sb->s_fs_info is set when a superblock is mounted and cleared when
> > superblock gets unmounted and otherwise it is never changed. So most likely
> > it was some memory corruption clearing that pointer (I wouldn't really
> > suspect HW here).
> > 
> > It somewhat looks like the issue described here:
> > http://lkml.indiana.edu/hypermail/linux/kernel/1202.3/00132.html
> > 
> > Although there we had f_path.dentry (completely different structure) being
> > NULL. But similarity here is that something stomped NULL over our existing
> > structure.
> > 
> > Linus, Jiri, that bug didn't get resolved, did it?
> 
> I am not aware of anything, but I have a question -- George, did the 
> machine get suspended/resumed before this happened?
  And by any chance, do you use i915 driver? Because that one seems to
cause corruption - see: https://lkml.org/lkml/2012/3/9/217. I believe
Jiri's corruption is likely caused by that...

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2012-03-16 10:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 13:39 Oops in ext3_block_to_path.isra.40+0x26/0x11b George Spelvin
2012-03-16  8:52 ` Jan Kara
2012-03-16  9:11   ` George Spelvin
2012-03-16  9:29   ` Jiri Kosina
2012-03-16 10:07     ` Jan Kara [this message]
2012-03-16 14:28     ` George Spelvin
2012-03-16 15:25       ` Jiri Kosina
2012-03-16 21:04         ` George Spelvin
2012-03-16 21:09           ` Linus Torvalds

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=20120316100728.GA28098@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=jkosina@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).