linux-kernel - Re: linux-next: OOPS at boot time

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: <1279617124_23571@mail4.comsite.net>
Date:	Tue, 20 Jul 2010 04:12:04 -0500
From:	Milton Miller <miltonm@....com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: linux-next: OOPS at boot time

> Hi Al,
> 
> All of my PowerPC boot tests are getting this after getting to user mode
> (sometimes several times):

> 
> This is:
> BUG_ON(inode->i_state != (I_FREEING | I_CLEAR));
> in iput_final().
> 
> That BUG_ON was added by commit c0ae81f2 ("Make ->drop_inode() just
> return whether inode needs to be dropped").
> 
> Has anyone seen this or something similar?

http://kerneltrap.org/mailarchive/linux-kernel/2010/7/8/4591460/thread

Looks like it died due to unable to reproduce ...

I don't need to be cc'd.

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