From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Juhyung Park <qkrwngud825@gmail.com>
Cc: Gao Xiang <xiang@kernel.org>,
linux-erofs@lists.ozlabs.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-crypto@vger.kernel.org,
Yann Collet <yann.collet.73@gmail.com>
Subject: Re: Weird EROFS data corruption
Date: Wed, 6 Dec 2023 11:11:37 +0800 [thread overview]
Message-ID: <4df2694d-5675-2baf-5825-55730a49e1b0@linux.alibaba.com> (raw)
In-Reply-To: <CAD14+f0PJiKVToxH6oULL6KuKqbKN+j6rcdwh7dpH8dHNZz42A@mail.gmail.com>
Hi Juhyung,
On 2023/12/5 22:43, Juhyung Park wrote:
> On Tue, Dec 5, 2023 at 11:34 PM Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
>>
...
>>
>> I'm still analyzing this behavior as well as the root cause and
>> I will also try to get a recent cloud server with FSRM myself
>> to find more clues.
>
> Down the rabbit hole we go...
>
> Let me know if you have trouble getting an instance with FSRM. I'll
> see what I can do.
I've sent out a fix to address this, please help check:
https://lore.kernel.org/r/20231206030758.3760521-1-hsiangkao@linux.alibaba.com
Thanks,
Gao Xiang
WARNING: multiple messages have this Message-ID (diff)
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Juhyung Park <qkrwngud825@gmail.com>
Cc: Yann Collet <yann.collet.73@gmail.com>,
linux-erofs@lists.ozlabs.org, linux-crypto@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Weird EROFS data corruption
Date: Wed, 6 Dec 2023 11:11:37 +0800 [thread overview]
Message-ID: <4df2694d-5675-2baf-5825-55730a49e1b0@linux.alibaba.com> (raw)
In-Reply-To: <CAD14+f0PJiKVToxH6oULL6KuKqbKN+j6rcdwh7dpH8dHNZz42A@mail.gmail.com>
Hi Juhyung,
On 2023/12/5 22:43, Juhyung Park wrote:
> On Tue, Dec 5, 2023 at 11:34 PM Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
>>
...
>>
>> I'm still analyzing this behavior as well as the root cause and
>> I will also try to get a recent cloud server with FSRM myself
>> to find more clues.
>
> Down the rabbit hole we go...
>
> Let me know if you have trouble getting an instance with FSRM. I'll
> see what I can do.
I've sent out a fix to address this, please help check:
https://lore.kernel.org/r/20231206030758.3760521-1-hsiangkao@linux.alibaba.com
Thanks,
Gao Xiang
WARNING: multiple messages have this Message-ID (diff)
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Juhyung Park <qkrwngud825@gmail.com>
Cc: Yann Collet <yann.collet.73@gmail.com>,
Gao Xiang <xiang@kernel.org>,
linux-erofs@lists.ozlabs.org, linux-crypto@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Weird EROFS data corruption
Date: Wed, 6 Dec 2023 11:11:37 +0800 [thread overview]
Message-ID: <4df2694d-5675-2baf-5825-55730a49e1b0@linux.alibaba.com> (raw)
In-Reply-To: <CAD14+f0PJiKVToxH6oULL6KuKqbKN+j6rcdwh7dpH8dHNZz42A@mail.gmail.com>
Hi Juhyung,
On 2023/12/5 22:43, Juhyung Park wrote:
> On Tue, Dec 5, 2023 at 11:34 PM Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
>>
...
>>
>> I'm still analyzing this behavior as well as the root cause and
>> I will also try to get a recent cloud server with FSRM myself
>> to find more clues.
>
> Down the rabbit hole we go...
>
> Let me know if you have trouble getting an instance with FSRM. I'll
> see what I can do.
I've sent out a fix to address this, please help check:
https://lore.kernel.org/r/20231206030758.3760521-1-hsiangkao@linux.alibaba.com
Thanks,
Gao Xiang
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-12-06 3:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 16:22 Weird EROFS data corruption Juhyung Park
2023-12-03 16:22 ` [f2fs-dev] " Juhyung Park
2023-12-03 16:22 ` Juhyung Park
2023-12-03 16:52 ` Gao Xiang
2023-12-03 16:52 ` [f2fs-dev] " Gao Xiang
2023-12-03 16:52 ` Gao Xiang
2023-12-03 17:01 ` Juhyung Park
2023-12-03 17:01 ` [f2fs-dev] " Juhyung Park
2023-12-03 17:01 ` Juhyung Park
2023-12-03 17:21 ` Gao Xiang
2023-12-03 17:21 ` [f2fs-dev] " Gao Xiang
2023-12-03 17:21 ` Gao Xiang
2023-12-03 17:32 ` Juhyung Park
2023-12-03 17:32 ` [f2fs-dev] " Juhyung Park
2023-12-03 17:32 ` Juhyung Park
2023-12-04 3:28 ` Gao Xiang
2023-12-04 3:28 ` [f2fs-dev] " Gao Xiang
2023-12-04 3:28 ` Gao Xiang
2023-12-04 3:41 ` Juhyung Park
2023-12-04 3:41 ` [f2fs-dev] " Juhyung Park
2023-12-04 3:41 ` Juhyung Park
2023-12-05 7:32 ` Gao Xiang
2023-12-05 7:32 ` [f2fs-dev] " Gao Xiang
2023-12-05 7:32 ` Gao Xiang
2023-12-05 14:23 ` Juhyung Park
2023-12-05 14:23 ` [f2fs-dev] " Juhyung Park
2023-12-05 14:23 ` Juhyung Park
2023-12-05 14:34 ` Gao Xiang
2023-12-05 14:34 ` [f2fs-dev] " Gao Xiang
2023-12-05 14:34 ` Gao Xiang
2023-12-05 14:43 ` Juhyung Park
2023-12-05 14:43 ` [f2fs-dev] " Juhyung Park
2023-12-05 14:43 ` Juhyung Park
2023-12-06 3:11 ` Gao Xiang [this message]
2023-12-06 3:11 ` [f2fs-dev] " Gao Xiang
2023-12-06 3:11 ` Gao Xiang
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=4df2694d-5675-2baf-5825-55730a49e1b0@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=qkrwngud825@gmail.com \
--cc=xiang@kernel.org \
--cc=yann.collet.73@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.