From: Christoph Hellwig <hch@infradead.org>
To: cheng.lin130@zte.com.cn
Cc: david@fromorbit.com, djwong@kernel.org,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
jiang.yong5@zte.com.cn, wang.liang82@zte.com.cn,
liu.dong3@zte.com.cn
Subject: Re: [PATCH v6] xfs: introduce protection for drop nlink
Date: Mon, 9 Oct 2023 23:57:27 -0700 [thread overview]
Message-ID: <ZST117zXotVPXGEQ@infradead.org> (raw)
In-Reply-To: <202310101009011817522@zte.com.cn>
On Tue, Oct 10, 2023 at 10:09:01AM +0800, cheng.lin130@zte.com.cn wrote:
> From: Cheng Lin <cheng.lin130@zte.com.cn>
>
> When abnormal drop_nlink are detected on the inode,
> return error, to avoid corruption propagation.
I know this has been through a few cycles, but wouldn't it be useful
to have at least a little description here how that case could happen?
next prev parent reply other threads:[~2023-10-10 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 2:09 [PATCH v6] xfs: introduce protection for drop nlink cheng.lin130
2023-10-10 6:57 ` Christoph Hellwig [this message]
2023-10-11 6:51 ` cheng.lin130
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=ZST117zXotVPXGEQ@infradead.org \
--to=hch@infradead.org \
--cc=cheng.lin130@zte.com.cn \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=jiang.yong5@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=liu.dong3@zte.com.cn \
--cc=wang.liang82@zte.com.cn \
/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