Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <72178179-cf1a-5a7b-67e1-0ceab01de685@huawei.com>
Date:   Wed, 15 Jun 2022 21:41:32 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.2.1
Subject: Re: Question about reporting unexpected wb err in nfs write()/flush()
To:     Trond Myklebust <trondmy@hammerspace.com>
CC:     "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
        "zhangxiaoxu5@huawei.com" <zhangxiaoxu5@huawei.com>
References: <ff6de37e-899a-8b23-d1a9-bf11fde10e5d@huawei.com>
 <1995185dc7899aca681cf70772e8e80c4a7faddd.camel@hammerspace.com>
From:   "chenxiaosong (A)" <chenxiaosong2@huawei.com>
In-Reply-To: <1995185dc7899aca681cf70772e8e80c4a7faddd.camel@hammerspace.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

在 2022/6/15 21:35, Trond Myklebust 写道:
> 
> No! That is still special casing the way NFS treats errors vs the way
> all other filesystems do.
> 
> Either the current VFS implementation of error logging is correct, or
> it is not. If it is incorrect, then let's fix it to do the right thing
> for everyone.
> 
> Either way, please stop posting these NFS-only workarounds.
> 

Thanks for your advice, I will try to fix the sequence error mechanism.