From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Chao Yu <chao@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH v3 1/5] f2fs: compress: add compress_inode to cache compressed blocks
Date: Fri, 29 Jan 2021 09:13:24 +0800 [thread overview]
Message-ID: <eb25281b-a40e-8965-cdf5-b7c461fbe195@huawei.com> (raw)
In-Reply-To: <YBLifNK5EXedfhbs@google.com>
On 2021/1/29 0:12, Jaegeuk Kim wrote:
> On 01/28, Chao Yu wrote:
>> On 2021/1/22 10:17, Chao Yu wrote:
>>>> No, it seems this is not the case.
>>> Oops, could you please help to remove all below codes and do the test again
>>> to check whether they are the buggy codes? as I doubt there is use-after-free
>>> bug.
>>
>> Any test result? :)
>
> It seems I don't see the errors anymore. Will you post another version?
No, your test result only indicate that bug was caused by race condition
of that line with high possibility, however I've no idea how that happen
after several round code review. Still struggling in troubleshooting this
issue.
Thanks,
>
>>
>> Thanks,
> .
>
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 1/5] f2fs: compress: add compress_inode to cache compressed blocks
Date: Fri, 29 Jan 2021 09:13:24 +0800 [thread overview]
Message-ID: <eb25281b-a40e-8965-cdf5-b7c461fbe195@huawei.com> (raw)
In-Reply-To: <YBLifNK5EXedfhbs@google.com>
On 2021/1/29 0:12, Jaegeuk Kim wrote:
> On 01/28, Chao Yu wrote:
>> On 2021/1/22 10:17, Chao Yu wrote:
>>>> No, it seems this is not the case.
>>> Oops, could you please help to remove all below codes and do the test again
>>> to check whether they are the buggy codes? as I doubt there is use-after-free
>>> bug.
>>
>> Any test result? :)
>
> It seems I don't see the errors anymore. Will you post another version?
No, your test result only indicate that bug was caused by race condition
of that line with high possibility, however I've no idea how that happen
after several round code review. Still struggling in troubleshooting this
issue.
Thanks,
>
>>
>> Thanks,
> .
>
_______________________________________________
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:[~2021-01-29 1:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 9:31 [PATCH v3 1/5] f2fs: compress: add compress_inode to cache compressed blocks Chao Yu
2021-01-07 9:31 ` [f2fs-dev] " Chao Yu
2021-01-11 9:48 ` Jaegeuk Kim
2021-01-11 9:48 ` [f2fs-dev] " Jaegeuk Kim
2021-01-11 10:31 ` Chao Yu
2021-01-11 10:31 ` [f2fs-dev] " Chao Yu
2021-01-11 11:45 ` Chao Yu
2021-01-11 11:45 ` Chao Yu
2021-01-12 1:33 ` Chao Yu
2021-01-12 1:33 ` Chao Yu
2021-01-12 2:04 ` Jaegeuk Kim
2021-01-12 2:04 ` Jaegeuk Kim
2021-01-12 9:02 ` Chao Yu
2021-01-12 9:02 ` Chao Yu
2021-01-12 22:36 ` Jaegeuk Kim
2021-01-12 22:36 ` Jaegeuk Kim
2021-01-13 1:09 ` Chao Yu
2021-01-13 1:09 ` Chao Yu
2021-01-13 15:41 ` Jaegeuk Kim
2021-01-13 15:41 ` Jaegeuk Kim
2021-01-14 2:45 ` Chao Yu
2021-01-14 2:45 ` Chao Yu
2021-01-14 4:06 ` Jaegeuk Kim
2021-01-14 4:06 ` Jaegeuk Kim
2021-01-15 9:32 ` Chao Yu
2021-01-15 9:32 ` Chao Yu
2021-01-15 14:59 ` Jaegeuk Kim
2021-01-15 14:59 ` Jaegeuk Kim
2021-01-16 12:07 ` Chao Yu
2021-01-16 12:07 ` Chao Yu
2021-01-19 21:42 ` Jaegeuk Kim
2021-01-19 21:42 ` Jaegeuk Kim
2021-01-22 2:17 ` Chao Yu
2021-01-22 2:17 ` Chao Yu
2021-01-28 2:50 ` Chao Yu
2021-01-28 2:50 ` Chao Yu
2021-01-28 16:12 ` Jaegeuk Kim
2021-01-28 16:12 ` Jaegeuk Kim
2021-01-29 1:13 ` Chao Yu [this message]
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=eb25281b-a40e-8965-cdf5-b7c461fbe195@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 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.