From: Eric Biggers <ebiggers@kernel.org>
To: Sahitya Tummala <stummala@codeaurora.org>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Satya Tangirala <satyat@google.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix use-after-free when accessing bio->bi_crypt_context
Date: Mon, 15 Jun 2020 08:47:20 -0700 [thread overview]
Message-ID: <20200615154720.GA902@sol.localdomain> (raw)
In-Reply-To: <20200615095316.GB2916@codeaurora.org>
On Mon, Jun 15, 2020 at 03:23:16PM +0530, Sahitya Tummala wrote:
> >
> > Should I fold this change into the original patch? Or keep it as a
> > separate patch when I send out the fscrypt/f2fs inline encryption
> > patches?
>
> It may be good to keep it seperate as we already have the base FBE patches in
> several downstream kernels, so this fix can be applied easily. But I will
> leave it up to you to take a call on this.
>
We should fold it in because the patch this fixes isn't applied upstream yet.
We'll need to submit this as a separate fix to the Android common kernels
because they already have a previous version of the inline encryption patchset.
(I assume that's where you have the code from.) But that doesn't affect what we
do upstream.
- Eric
_______________________________________________
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:[~2020-06-15 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 3:59 [f2fs-dev] [PATCH] f2fs: fix use-after-free when accessing bio->bi_crypt_context Sahitya Tummala
2020-06-15 5:00 ` Eric Biggers
2020-06-15 6:16 ` Satya Tangirala via Linux-f2fs-devel
2020-06-15 9:53 ` Sahitya Tummala
2020-06-15 15:47 ` Eric Biggers [this message]
2020-06-16 1:36 ` Sahitya Tummala
2020-06-15 9:48 ` Sahitya Tummala
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=20200615154720.GA902@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=satyat@google.com \
--cc=stummala@codeaurora.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).