mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>, <chao@kernel.org>
Subject: Re: [PATCH v3 1/5] f2fs: compress: add compress_inode to cache compressed blocks
Date: Mon, 11 Jan 2021 18:31:53 +0800	[thread overview]
Message-ID: <6b0060b9-460a-617a-3778-e67f35d551f0@huawei.com> (raw)
In-Reply-To: <X/we0NoUqAwuW82+@google.com>

On 2021/1/11 17:48, Jaegeuk Kim wrote:
> Hi Chao,
> 
> After quick test of fsstress w/ fault injection, it gave wrong block address
> errors. Could you please run the test a bit?

Jaegeuk,

Oh, I've covered with fstest cases and there is no such error message, let me
try fault injection + SPO case soon.

Thanks,


  reply	other threads:[~2021-01-11 10:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07  9:31 Chao Yu
2021-01-11  9:48 ` Jaegeuk Kim
2021-01-11 10:31   ` Chao Yu [this message]
2021-01-11 11:45     ` [f2fs-dev] " Chao Yu
2021-01-12  1:33       ` Chao Yu
2021-01-12  2:04         ` Jaegeuk Kim
2021-01-12  9:02           ` Chao Yu
2021-01-12 22:36             ` Jaegeuk Kim
2021-01-13  1:09               ` Chao Yu
2021-01-13 15:41                 ` Jaegeuk Kim
2021-01-14  2:45                   ` Chao Yu
2021-01-14  4:06                     ` Jaegeuk Kim
2021-01-15  9:32                       ` Chao Yu
2021-01-15 14:59                         ` Jaegeuk Kim
2021-01-16 12:07                           ` Chao Yu
2021-01-19 21:42                             ` Jaegeuk Kim
2021-01-22  2:17                               ` Chao Yu
2021-01-28  2:50                                 ` Chao Yu
2021-01-28 16:12                                   ` Jaegeuk Kim
2021-01-29  1:13                                     ` Chao Yu

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=6b0060b9-460a-617a-3778-e67f35d551f0@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@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®