From: Valdis.Kletnieks@vt.edu
To: yi zhang <yi.zhang@huawei.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca
Subject: Re: [RFC PATCH] ext4: increase the protection of drop nlink and ext4 inode destroy
Date: Sat, 31 Dec 2016 17:59:13 -0500 [thread overview]
Message-ID: <141922.1483225153@turing-police.cc.vt.edu> (raw)
In-Reply-To: <1482755657-28791-1-git-send-email-yi.zhang@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On Mon, 26 Dec 2016 20:34:17 +0800, yi zhang said:
> Because of the disk and hardware issue, the ext4 filesystem have
> many errors, the inode->i_nlink of ext4 becomes zero abnormally
> but the dentry is still positive, it will cause memory corruption
> after the following process:
>
> 1) Due to the inode->i_nlink is 0, this inode will be added into
> the orhpan list,
> + if (WARN(inode->i_nlink == 0, "inode %lu nlink"
> + " is already 0", inode->i_ino))
Can we get the filesystem? Or at least the device major/minor? If a system
has multiple large ext4 filesystems, it would be helpful to know which
one is having the problem.
[-- Attachment #2: Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2016-12-31 22:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 12:34 yi zhang
2016-12-26 18:32 ` Andreas Dilger
2016-12-31 22:59 ` Valdis.Kletnieks [this message]
2017-01-04 8:29 ` zhangyi (F)
2017-01-04 21:54 ` Darrick J. Wong
2017-01-04 22:00 ` Andreas Dilger
2017-01-04 23:35 ` Theodore Ts'o
2017-01-05 7:24 ` zhangyi (F)
2017-01-05 17:38 ` Darrick J. Wong
2017-01-11 9:07 ` zhangyi (F)
2017-01-11 15:34 ` Theodore Ts'o
2017-01-12 8:00 ` zhangyi (F)
2017-01-12 17:03 ` Theodore Ts'o
2017-01-13 3:42 ` Al Viro
2017-01-13 14:26 ` Theodore Ts'o
2017-01-16 3:24 ` zhangyi (F)
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=141922.1483225153@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.com \
/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
all inboxes | Powered by JetHome®