lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 15 May 2008 16:35:50 +0200
From:	Jan Kara <jack@...e.cz>
To:	Vegard Nossum <vegard.nossum@...il.com>
Cc:	linux-ext4@...r.kernel.org, sct@...hat.com,
	akpm@...ux-foundation.org, adilger@...sterfs.com
Subject: Re: BUG in ext3_sync_fs

  Hi,

> With current git (+ kmemcheck, see below) patches I get the following
> during boot:
> 
> BUG: unable to handle kernel paging request at 00001108
> IP: [<c04effcf>] ext3_sync_fs+0x3f/+x80
> 
> I inserted some printks in ext3_sync_fs():
>         printk(KERN_EMERG "sb = %p\n", sb);
>         printk(KERN_EMERG "sb->s_fs_info = %p\n", sb->s_fs_info);
> 
> And they show:
> sb = f7f61e00
> sb->s_fs_info = 00000000
> 
> Monitorshot: http://folk.uio.no/vegardno/linux/DSCF2905.JPG
> Config: http://folk.uio.no/vegardno/linux/config-20080501.txt
> 
> I am booting a USB stick with an ext2 filesystem as root partition. It
> mounts fine in other machines.
> 
> It could of course be my kmemcheck patches that are causing this
> (though I find it unlikely as they are disabled on boot => no-op, and
> everything was fine a couple of days ago), but recompiling this config
> takes a few hours, and I thought I'd just post early in case the
> problem is really with ext3.
> 
> I can send vmlinux image and/or disk image if necessary.
  Looks like a bug introduced by quota change - it should be fixed in
the current Linus's kernel. Thanks for report anyway.

								Honza
-- 
Jan Kara <jack@...e.cz>
SuSE CR Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ