From: Matthew Wilcox <willy@infradead.org>
To: Christoph Lameter <cl@linux.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@lge.com,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: copy_page() on a kmalloc-ed page with DEBUG_SLAB enabled (was "zram: do not use copy_page with non-page alinged address")
Date: Tue, 18 Apr 2017 06:13:49 -0700 [thread overview]
Message-ID: <20170418131349.GA18505@bombadil.infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1704171016550.28407@east.gentwo.org>
On Mon, Apr 17, 2017 at 10:20:42AM -0500, Christoph Lameter wrote:
> Simple solution is to not allocate pages via the slab allocator but use
> the page allocator for this. The page allocator provides proper alignment.
>
> There is a reason it is called the page allocator because if you want a
> page you use the proper allocator for it.
Previous discussion on this topic:
https://lwn.net/Articles/669015/
https://lwn.net/Articles/669020/
prev parent reply other threads:[~2017-04-18 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 1:48 copy_page() on a kmalloc-ed page with DEBUG_SLAB enabled (was "zram: do not use copy_page with non-page alinged address") Sergey Senozhatsky
2017-04-17 15:20 ` Christoph Lameter
2017-04-18 0:03 ` Minchan Kim
2017-04-18 7:33 ` Michal Hocko
2017-04-18 10:56 ` Sergey Senozhatsky
2017-04-18 11:06 ` Michal Hocko
2017-04-19 6:11 ` Sergey Senozhatsky
2017-04-19 6:02 ` Minchan Kim
2017-04-19 11:51 ` Matthew Wilcox
2017-04-20 1:45 ` Sergey Senozhatsky
2017-04-20 6:50 ` Minchan Kim
2017-04-18 10:42 ` Sergey Senozhatsky
2017-04-18 13:28 ` Christoph Lameter
2017-04-18 13:13 ` Matthew Wilcox [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=20170418131349.GA18505@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=vbabka@suse.cz \
/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).