From: Salvatore Bonaccorso <carnil@debian.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: butt3rflyh4ck <butterflyhuangxx@gmail.com>,
jaegeuk@kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid out-of-bounds memory access
Date: Tue, 20 Apr 2021 19:43:24 +0200 [thread overview]
Message-ID: <YH8SvK+OLSKAEYpJ@eldamar.lan> (raw)
In-Reply-To: <beff8953-d91a-c677-f50a-3aba27c15dde@huawei.com>
Hi,
On Tue, Mar 23, 2021 at 02:43:29PM +0800, Chao Yu wrote:
> Hi butt3rflyh4ck,
>
> On 2021/3/23 13:48, butt3rflyh4ck wrote:
> > Hi, I have tested the patch on 5.12.0-rc4+, it seems to fix the problem.
>
> Thanks for helping to test this patch.
Was this patch applied? I do not see it in mainline (unless
miss-checked).
Regards,
Salvatore
next prev parent reply other threads:[~2021-04-20 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 11:47 [PATCH] f2fs: fix to avoid out-of-bounds memory access Chao Yu
2021-03-23 5:48 ` butt3rflyh4ck
2021-03-23 6:43 ` Chao Yu
2021-04-20 17:43 ` Salvatore Bonaccorso [this message]
2021-04-20 18:27 ` [f2fs-dev] " Jaegeuk Kim
2021-04-20 18:34 ` butt3rflyh4ck
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=YH8SvK+OLSKAEYpJ@eldamar.lan \
--to=carnil@debian.org \
--cc=butterflyhuangxx@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).