[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20131120144014.386293ce24e7b298ebab7b8e@linux-foundation.org>
Date: Wed, 20 Nov 2013 14:40:14 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Al Viro <viro@...iv.linux.org.uk>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [git pull] vfs.git bits and pieces
On Wed, 20 Nov 2013 14:33:35 -0800 Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> On Wed, Nov 20, 2013 at 9:47 AM, Al Viro <viro@...iv.linux.org.uk> wrote:
> >
> > BTW, something odd happened to mm/memory.c - either a mangled patch
> > or a lost followup:
> >
> > commit ea1e7ed33708
> > mm: create a separate slab for page->ptl allocation
> >
> > Fair enough, and yes, it does create that separate slab. The problem is,
> > it's still using kmalloc/kfree for those beasts - page_ptl_cachep isn't
> > used at all...
>
> Ok, it looks straightforward enough to just replace the kmalloc/kfree
> with using a slab allocation using the page_ptl_cachep pointer. I'd do
> it myself, but I would like to know how it got lost? Also, much
> testing to make sure the cachep is initialized early enough.
agh, I went through hell keeping that patch alive and it appears I lost
some of it.
> Or should we just revert the commit that added the pointless/unused
> slab pointer?
>
> Andrew, Kirill, comments?
Let's just kill it please. We can try again for 3.14.
> Also note the other issue Al found: see commit 2a46eed54a28 ("Wrong
> page freed on preallocate_pmds() failure exit") that I just pushed
> out.
lgtm, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists