From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Randall Huang <huangrandall@google.com>,
<linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] f2fs: fix to avoid accessing xattr across the boundary
Date: Fri, 10 May 2019 09:14:12 +0800 [thread overview]
Message-ID: <57a8cf36-af86-8d4b-856d-e7d70cf2d098@huawei.com> (raw)
In-Reply-To: <20190509164814.GA79912@jaegeuk-macbookpro.roam.corp.google.com>
On 2019/5/10 0:48, Jaegeuk Kim wrote:
> Okay, how about this?
>
>>From 2777e654371dd4207a3a7f4fb5fa39550053a080 Mon Sep 17 00:00:00 2001
> From: Randall Huang <huangrandall@google.com>
> Date: Thu, 11 Apr 2019 16:26:46 +0800
> Subject: [PATCH] f2fs: fix to avoid accessing xattr across the boundary
Looks good to me, and more clean. :)
Thanks,
prev parent reply other threads:[~2019-05-10 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 8:26 [PATCH v5] f2fs: fix to avoid accessing xattr across the boundary Randall Huang
2019-04-12 2:05 ` Chao Yu
2019-05-09 4:15 ` Jaegeuk Kim
2019-05-09 7:07 ` Chao Yu
2019-05-09 16:48 ` Jaegeuk Kim
2019-05-10 1:14 ` Chao Yu [this message]
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=57a8cf36-af86-8d4b-856d-e7d70cf2d098@huawei.com \
--to=yuchao0@huawei.com \
--cc=huangrandall@google.com \
--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;
as well as URLs for NNTP newsgroup(s).