From: Alex <alex.vizor@gmail.com>
To: Theodore Tso <tytso@MIT.EDU>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org
Subject: Re: WARNING: at fs/inode.c:884 unlock_new_inode+0x34/0x59()
Date: Mon, 28 Nov 2011 22:08:50 +0300 [thread overview]
Message-ID: <4ED3DC42.20504@gmail.com> (raw)
In-Reply-To: <0F03D476-02D9-4C10-8A4D-7949E5B07CBB@mit.edu>
On 11/28/2011 09:28 PM, Theodore Tso wrote:
> 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
>
Yes I can reproduce this, it happens after every s2disk.
Tanks,
Alex
next prev parent reply other threads:[~2011-11-28 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ED2994A.9080907@gmail.com>
2011-11-27 20:24 ` WARNING: at fs/inode.c:884 unlock_new_inode+0x34/0x59() Alex
2011-11-27 21:34 ` Ted Ts'o
2011-11-28 12:38 ` Alexander Zhavnerchik
[not found] ` <4ED3CF24.2050702@gmail.com>
2011-11-28 18:28 ` Theodore Tso
2011-11-28 19:08 ` Alex [this message]
2011-12-01 22:33 ` Eric Sandeen
2011-12-05 20:54 ` Eric Sandeen
2011-12-05 21:07 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ED3DC42.20504@gmail.com \
--to=alex.vizor@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@MIT.EDU \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).