Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1548842

Re: [RFC PATCH] ext4: increase the protection of drop nlink and ext4 inode destroy

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

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.

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[RFC PATCH] ext4: increase the protection of drop nlink and ext4  inode destroy yi zhang <yi.zhang@huawei.com> - 2016-12-26 13:40 +0100
  Re: [RFC PATCH] ext4: increase the protection of drop nlink and ext4  inode destroy Andreas Dilger <adilger@dilger.ca> - 2016-12-26 19:40 +0100
  Re: [RFC PATCH] ext4: increase the protection of drop nlink and ext4 inode destroy Valdis.Kletnieks@vt.edu - 2017-01-01 00:00 +0100

csiph-web