linux-ext4 - Re: WARNING: at fs/inode.c:884 unlock_new

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-next>] [day] [month] [year] [list]

Message-Id: <0F03D476-02D9-4C10-8A4D-7949E5B07CBB@mit.edu>
Date:	Mon, 28 Nov 2011 13:28:53 -0500
From:	Theodore Tso <tytso@....EDU>
To:	Alex <alex.vizor@...il.com>
Cc:	Theodore Tso <tytso@....edu>, adilger.kernel@...ger.ca,
	linux-ext4@...r.kernel.org
Subject: Re: WARNING: at fs/inode.c:884 unlock_new_inode+0x34/0x59()

On Nov 28, 2011, at 1:12 PM, Alex wrote:

> Hi Ted,
> 
> This is full dmesg with suspend to disk. This time no fs errors happened. And unfortunately I don't remember what kind of errors were there last time.
> 

OK, so you have a very large number of warnings, spanning over several seconds.   That sounds to me like a memory corruption problem, as opposed to some kind of race that only happens for a symlink creation happening right during the suspend/resume.

I can fix the warning and arrange to print more debugging information so that if this happens again, we get more information, but if you can't reproduce it, I'm not sure there's much more I can do for now.

Regards,

-- Ted

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