All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix leaking uninitialized memory in compressed clusters
Date: Thu, 27 Feb 2020 10:16:06 -0800	[thread overview]
Message-ID: <20200227181606.GB33965@google.com> (raw)
In-Reply-To: <20200227180854.GA877@sol.localdomain>

On 02/27, Eric Biggers wrote:
> On Tue, Feb 25, 2020 at 04:53:02PM +0800, Chao Yu wrote:
> > On 2020/2/21 12:50, Eric Biggers wrote:
> > > From: Eric Biggers <ebiggers@google.com>
> > > 
> > > When the compressed data of a cluster doesn't end on a page boundary,
> > > the remainder of the last page must be zeroed in order to avoid leaking
> > > uninitialized memory to disk.
> > > 
> > > Fixes: 4c8ff7095bef ("f2fs: support data compression")
> > > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > 
> > Reviewed-by: Chao Yu <yuchao0@huawei.com>
> > 
> 
> Jaegeuk, can you send this fix to Linus for 5.6?

Okay.

> 
> - Eric


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2020-02-27 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21  4:50 [f2fs-dev] [PATCH] f2fs: fix leaking uninitialized memory in compressed clusters Eric Biggers
2020-02-25  8:53 ` Chao Yu
2020-02-27 18:08   ` Eric Biggers
2020-02-27 18:16     ` Jaegeuk Kim [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=20200227181606.GB33965@google.com \
    --to=jaegeuk@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.