mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Richard Weinberger <richard@nod.at>, <linux-mtd@lists.infradead.org>
Cc: <david@sigma-star.at>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>
Subject: Re: [PATCH 3/4] ubifs: Update directory size when creating whiteouts
Date: Mon, 25 Jan 2021 09:05:48 +0800	[thread overview]
Message-ID: <cca6ac4f-4739-76be-9b48-b3643017a556@huawei.com> (raw)
In-Reply-To: <5b51ff9c-8f5e-c348-5195-c0a0bf60b746@huawei.com>

在 2021/1/23 10:45, Zhihao Cheng 写道:

>> @@ -430,6 +433,7 @@ static int do_tmpfile(struct inode *dir, struct 
>> dentry *dentry,
>>       return 0;
>>   out_cancel:
Still one question:
> Does this need a judgment? Like this,
> if (whiteout)
>      dir->i_size -= sz_change;

>> +    dir->i_size -= sz_change;
>>       mutex_unlock(&dir_ui->ui_mutex);
>>   out_inode:
>>       make_bad_inode(inode);
>>
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/


  parent reply	other threads:[~2021-01-25  1:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 21:22 [PATCH 0/4] Assorted UBIFS fixes Richard Weinberger
2021-01-22 21:22 ` [PATCH 1/4] ubifs: Correctly set inode size in ubifs_link() Richard Weinberger
2021-01-23  2:35   ` Zhihao Cheng
2021-01-22 21:22 ` [PATCH 2/4] ubifs: Don't add fscrypt context to xattrs Richard Weinberger
2021-01-22 21:22 ` [PATCH 3/4] ubifs: Update directory size when creating whiteouts Richard Weinberger
2021-01-23  2:45   ` Zhihao Cheng
2021-01-23 10:05     ` Richard Weinberger
2021-01-25  1:05     ` Zhihao Cheng [this message]
2021-01-25  7:55       ` Richard Weinberger
2021-01-25  9:31         ` Zhihao Cheng
2021-01-22 21:22 ` [PATCH 4/4] ubifs: Harden ubifs_jnl_write_inode() Richard Weinberger

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=cca6ac4f-4739-76be-9b48-b3643017a556@huawei.com \
    --to=chengzhihao1@huawei.com \
    --cc=david@sigma-star.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=stable@vger.kernel.org \
    /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®