From: Christopher Lameter <cl@linux.com>
To: Waiman Long <longman@redhat.com>
Cc: Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Changbin Du <changbin.du@gmail.com>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v2] mm/slub: Fix incorrect interpretation of s->offset
Date: Mon, 27 Apr 2020 16:10:31 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.21.2004271606390.26716@www.lameter.com> (raw)
In-Reply-To: <20200427140822.18619-1-longman@redhat.com>
On Mon, 27 Apr 2020, Waiman Long wrote:
>
> To fix it, use the check "s->offset == s->inuse" in the new helper
> function freeptr_after_object() instead. Also add another helper function
> get_info_end() to return the end of info block (inuse + free pointer
> if not overlapping with object).
>
> Fixes: 3202fa62fb43 ("slub: relocate freelist pointer to middle of object")
> Signed-off-by: Waiman Long <longman@redhat.com>
> ---
> mm/slub.c | 37 ++++++++++++++++++++++---------------
> 1 file changed, 22 insertions(+), 15 deletions(-)
>
> diff --git a/mm/slub.c b/mm/slub.c
> index 0e736d66bb42..68f1b4b1c309 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -551,15 +551,29 @@ static void print_section(char *level, char *text, u8 *addr,
> metadata_access_disable();
> }
>
> +static inline bool freeptr_after_object(struct kmem_cache *s)
bool freeptr_outside_of_object()?
> +{
> + return s->offset == s->inuse;
s->offset >= s->inuse?
There may be a redzone after the object.
> +static inline unsigned int get_info_end(struct kmem_cache *s)
static inline track_offset()?
next prev parent reply other threads:[~2020-04-27 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 14:08 Waiman Long
2020-04-27 14:22 ` Matthew Wilcox
2020-04-27 16:10 ` Christopher Lameter [this message]
2020-04-27 17:42 ` Waiman Long
2020-04-27 17:49 ` Waiman Long
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=alpine.DEB.2.21.2004271606390.26716@www.lameter.com \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=changbin.du@gmail.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=willy@infradead.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