mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matthew Wilcox <mawilcox@microsoft.com>,
	"Linux F2FS DEV,
	Mailing List"  <linux-f2fs-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] f2fs update for 4.18-rc1
Date: Mon, 11 Jun 2018 10:40:10 -0700	[thread overview]
Message-ID: <20180611174010.GC6783@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <CA+55aFznP4aEy7DkVfeQ_e6eXgLnswVnSJS3C51UHD_k8qYZCA@mail.gmail.com>

On 06/11, Linus Torvalds wrote:
> On Mon, Jun 11, 2018 at 9:52 AM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> >
> > In order to avoid old MM bug [1], we decided not to use __GFP_ZERO
> > for the mapping for node and meta page caches.
> >
> > [1] https://lkml.org/lkml/2018/4/8/661
> 
> Hmm. The patch there looks correct, and anybody who relies on slab
> constructors is crazy.
> 
> That email from April says it should go into stable, but it never even
> went upstream..

Heh, I forgot to link the latest results. The MM fix was merged by:

abc1be13fd11 ("mm/filemap.c: fix NULL pointer in page_cache_tree_insert()")

Thanks,

> 
> Adding Willy to the cc, for comments, since he's been active there and
> is probably the maintainer even if the MAINTAINERS file doesn't say
> so..
> 
> Willy?
> 
>              Linus

  reply	other threads:[~2018-06-11 17:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11 16:52 Jaegeuk Kim
2018-06-11 17:27 ` Linus Torvalds
2018-06-11 17:40   ` Jaegeuk Kim [this message]
2018-06-11 17:43     ` Linus Torvalds
2018-06-11 18:20   ` Matthew Wilcox
2018-06-11 18:54     ` Linus Torvalds
2018-06-11 19:09     ` Jaegeuk Kim
2018-06-11 17:34 ` Linus Torvalds
2018-06-11 17:51   ` Jaegeuk Kim

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=20180611174010.GC6783@jaegeuk-macbookpro.roam.corp.google.com \
    --to=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mawilcox@microsoft.com \
    --cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®