From: Haifeng Xu <haifeng.xu@shopee.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: miklos@szeredi.hu, linux-unionfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ovl: don't set the superblock's errseq_t manually
Date: Mon, 29 Jul 2024 17:22:41 +0800 [thread overview]
Message-ID: <fc34fb9b-8afd-4f83-9e5a-e648b3358e90@shopee.com> (raw)
In-Reply-To: <CAOQ4uxi4B8JHYHF=yn6OrRZCdkoPUj3-+PuZTZy6iJR7RNWcbA@mail.gmail.com>
On 2024/7/29 14:43, Amir Goldstein wrote:
> On Mon, Jul 29, 2024 at 6:43 AM Haifeng Xu <haifeng.xu@shopee.com> wrote:
>>
>> Since commit 5679897eb104 ("vfs: make sync_filesystem return errors from
>> ->sync_fs"), the return value from sync_fs callback can be seen in
>> sync_filesystem(). Thus the errseq_set opreation can be removed here.
>>
>> Signed-off-by: Haifeng Xu <haifeng.xu@shopee.com>
>
> I would add either Fixes: or Depends-on: to prevent accidental
> backporting without the dependency.
OK, I'll add this in next version. Thanks!
>
> Otherwise you may add:
> Reviewed-by: Amir Goldstein <amir73il@gmail.com>
>
> Thanks,
> Amir.
>
>> ---
>> fs/overlayfs/super.c | 10 ++--------
>> 1 file changed, 2 insertions(+), 8 deletions(-)
>>
>> diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
>> index 06a231970cb5..fe511192f83c 100644
>> --- a/fs/overlayfs/super.c
>> +++ b/fs/overlayfs/super.c
>> @@ -202,15 +202,9 @@ static int ovl_sync_fs(struct super_block *sb, int wait)
>> int ret;
>>
>> ret = ovl_sync_status(ofs);
>> - /*
>> - * We have to always set the err, because the return value isn't
>> - * checked in syncfs, and instead indirectly return an error via
>> - * the sb's writeback errseq, which VFS inspects after this call.
>> - */
>> - if (ret < 0) {
>> - errseq_set(&sb->s_wb_err, -EIO);
>> +
>> + if (ret < 0)
>> return -EIO;
>> - }
>>
>> if (!ret)
>> return ret;
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2024-07-29 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 3:43 [PATCH] ovl: don't set the superblock's errseq_t manually Haifeng Xu
2024-07-29 6:43 ` Amir Goldstein
2024-07-29 9:22 ` Haifeng Xu [this message]
2024-07-30 4:20 ` [PATCH v2] " Haifeng Xu
2024-08-30 13:27 ` Amir Goldstein
2024-08-30 15:26 ` Darrick J. Wong
2024-09-02 11:32 ` Haifeng Xu
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=fc34fb9b-8afd-4f83-9e5a-e648b3358e90@shopee.com \
--to=haifeng.xu@shopee.com \
--cc=amir73il@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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