linux-kernel - Re: XFS: Assertion failed: xfs_dir2_sf_lookup(args) == ENOENT, file: fs/xfs/xfs_dir2

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: <20130713150650.GA31035@redhat.com>
Date:	Sat, 13 Jul 2013 11:06:50 -0400
From:	Dave Jones <davej@...hat.com>
To:	Dave Chinner <david@...morbit.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>, xfs@....sgi.com
Subject: Re: XFS: Assertion failed: xfs_dir2_sf_lookup(args) == ENOENT, file:
 fs/xfs/xfs_dir2_sf.c, line: 358

On Sat, Jul 13, 2013 at 12:00:30PM +1000, Dave Chinner wrote:
 > On Thu, Jul 11, 2013 at 10:39:30PM -0400, Dave Jones wrote:
 > > Just saw this during boot after an unclean shutdown. It hung afterwards.
 > > 
 > > [   97.162665] XFS: Assertion failed: xfs_dir2_sf_lookup(args) == ENOENT, file: fs/xfs/xfs_dir2_sf.c, line: 358
 > ....
 > > [   97.173730]  [<ffffffffa0076953>] xfs_dir2_sf_addname+0x43/0x760 [xfs]
 > > [   97.173743]  [<ffffffffa0067cfc>] xfs_dir_createname+0x15c/0x1b0 [xfs]
 > > [   97.173754]  [<ffffffffa002f2dc>] xfs_create+0x4cc/0x710 [xfs]
 > > [   97.173764]  [<ffffffffa00278ca>] xfs_vn_mknod+0x9a/0x1c0 [xfs]
 > > [   97.173773]  [<ffffffffa0027a03>] xfs_vn_create+0x13/0x20 [xfs]
 > > [   97.173776]  [<ffffffff811d100d>] vfs_create+0x9d/0x100
 > > [   97.173778]  [<ffffffff811d1995>] do_last+0x925/0xe00
 > > [   97.173780]  [<ffffffff811d1f2e>] path_openat+0xbe/0x6f0
 > > [   97.173783]  [<ffffffff8109e33f>] ? local_clock+0x3f/0x50
 > > [   97.173785]  [<ffffffff811e1b5f>] ? __alloc_fd+0xaf/0x200
 > > [   97.173787]  [<ffffffff811d2c3a>] do_filp_open+0x3a/0x90
 > > [   97.173789]  [<ffffffff811e1b5f>] ? __alloc_fd+0xaf/0x200
 > > [   97.173790]  [<ffffffff811c0ddb>] do_sys_open+0x10b/0x200
 > > [   97.173792]  [<ffffffff81010578>] ? syscall_trace_enter+0x18/0x290
 > > [   97.173794]  [<ffffffff811c0eee>] SyS_open+0x1e/0x20
 > > 
 > > This trace repeated a few times, then the same assertion was triggered from sys_renameat.
 > 
 > That's rather curious. What this means is that there is either an
 > EIO or EEXIST error being returned from xfs_dir2_sf_lookup() when a
 > we're about to add the new entry. There are two things here - EIO
 > can only be returned if a shutdown has occurred - are there any
 > signs of a shutdown in the logs?

not that I recall (machine is off, and remote right now).
1st time it was during boot (above), and 2nd time I hit it
the machine kept fuzzing for a while afterwards.

I'll see if I can reproduce it again on monday, and if so I'll
grab an xfsdump for you to stare at.

	Dave
--
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/