From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: butt3rflyh4ck <butterflyhuangxx@gmail.com>,
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 11:27:49 -0700 [thread overview]
Message-ID: <YH8dJQCJm7iqsC+a@google.com> (raw)
In-Reply-To: <YH8SvK+OLSKAEYpJ@eldamar.lan>
Hi,
On 04/20, Salvatore Bonaccorso wrote:
> 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).
Not yet. Queue for next merge window.
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev&id=b862676e371715456c9dade7990c8004996d0d9e
>
> Regards,
> Salvatore
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Chao Yu <yuchao0@huawei.com>,
butt3rflyh4ck <butterflyhuangxx@gmail.com>,
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 11:27:49 -0700 [thread overview]
Message-ID: <YH8dJQCJm7iqsC+a@google.com> (raw)
In-Reply-To: <YH8SvK+OLSKAEYpJ@eldamar.lan>
Hi,
On 04/20, Salvatore Bonaccorso wrote:
> 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).
Not yet. Queue for next merge window.
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev&id=b862676e371715456c9dade7990c8004996d0d9e
>
> Regards,
> Salvatore
next prev parent reply other threads:[~2021-04-20 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 11:47 [f2fs-dev] [PATCH] f2fs: fix to avoid out-of-bounds memory access Chao Yu
2021-03-22 11:47 ` Chao Yu
2021-03-23 5:48 ` [f2fs-dev] " butt3rflyh4ck
2021-03-23 5:48 ` butt3rflyh4ck
2021-03-23 6:43 ` [f2fs-dev] " Chao Yu
2021-03-23 6:43 ` Chao Yu
2021-04-20 17:43 ` [f2fs-dev] " Salvatore Bonaccorso
2021-04-20 17:43 ` Salvatore Bonaccorso
2021-04-20 18:27 ` Jaegeuk Kim [this message]
2021-04-20 18:27 ` Jaegeuk Kim
2021-04-20 18:34 ` butt3rflyh4ck
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=YH8dJQCJm7iqsC+a@google.com \
--to=jaegeuk@kernel.org \
--cc=butterflyhuangxx@gmail.com \
--cc=carnil@debian.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.