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] [thread-next>] [day] [month] [year] [list]
Message-Id: <201101070929.28672.florian@kriener.org>
Date:	Fri, 7 Jan 2011 09:29:28 +0100
From:	Florian Kriener <florian@...ener.org>
To:	Nick Piggin <npiggin@...il.com>
Cc:	linux-kernel@...r.kernel.org, Al Viro <viro@...iv.linux.org.uk>
Subject: Re: BUG in fs/inode.c:429

On Friday 07 January 2011 01:44:49 you wrote:
> On Fri, Jan 7, 2011 at 3:35 AM, Florian Kriener <florian@...ener.org> 
> > [ 4626.750273] ------------[ cut here ]------------
> > [ 4626.750314] kernel BUG at
> > /build/buildd-linux-2.6_2.6.37~rc7-1~experimental.1-amd64-
> > Mw4Tor/linux-2.6-2.6.37~rc7/debian/build/source_amd64_none/fs/inod
> > e.c:429!
> 
> Is this an unpatched kernel? ie.
> BUG_ON(!list_empty(&inode->i_data.private_list));

I checked, and yes, that's the line.
 
> > I am using 2.6.37-rc7 from Debian experimental and all my
> > filesystems are ext4 except for /boot, which is ext2 (and /tmp is
> > tmpfs).
> 
> Definitely no other filesystems? Too bad frame pointers are turned
> off, but it seems perhaps default evict_inode is being used, which
> doesn't do invalidate_inode_buffers(). ext2/3/4/fat/udf all seem to
> do the right thing here, though.

% mount
/dev/mapper/nanuk-root on / type ext4 (rw,noatime,errors=remount-ro,acl,commit=0)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sda1 on /boot type ext2 (rw,noatime)
tempfs on /tmp type tmpfs (rw,noatime,mode=1777)
/dev/mapper/nanuk-home on /home type ext4 (rw,noatime,acl,commit=0)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)

and that's all. I have an external hard drive, that is not shown above, but
its ext4 there too.
 
> If it's happening semi frequently, could you compile a vanilla 2.6.37
> with the same .config, just turn on frame pointers, and report if it
> happens again?

I'll do that. But I don't know how to turn frame pointers on. Is that a config
option? I only know of the -fomit-frame-pointers gcc option. If I understand
correctly that would be a small to medium performance hit, am I right?

> Dumping the inode->i_ops symbol name before going BUG in fact
> might be helpful too.

Again, I'll do that if you tell me how to.

Sorry for beeing such a noop.

Thanks,
Flo.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ