From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Dongli Zhang <dongli.zhang@oracle.com>
Cc: Eugeniu Rosca <erosca@de.adit-jv.com>,
Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<stable@vger.kernel.org>, Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: [PATCH] mm: slub: fix conversion of freelist_corrupted()
Date: Fri, 14 Aug 2020 09:46:44 +0200 [thread overview]
Message-ID: <20200814074644.GA7943@lxhi-065.adit-jv.com> (raw)
In-Reply-To: <f93a9f06-8608-6f28-27c0-b17f86dca55b@oracle.com>
Hello Dongli,
On Thu, Aug 13, 2020 at 11:57:51PM -0700, Dongli Zhang wrote:
> On 8/11/20 5:46 AM, Eugeniu Rosca wrote:
> > Commit 52f23478081ae0 ("mm/slub.c: fix corrupted freechain in
> > deactivate_slab()") suffered an update when picked up from LKML [1].
> >
> > Specifically, relocating 'freelist = NULL' into 'freelist_corrupted()'
> > created a no-op statement. Fix it by sticking to the behavior intended
> > in the original patch [1]. Prefer the lowest-line-count solution.
> >
> > [1] https://lore.kernel.org/linux-mm/20200331031450.12182-1-dongli.zhang@oracle.com/
> >
> > Fixes: 52f23478081ae0 ("mm/slub.c: fix corrupted freechain in deactivate_slab()")
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Cc: Dongli Zhang <dongli.zhang@oracle.com>
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com>
> > ---
> > mm/slub.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/mm/slub.c b/mm/slub.c
> > index 68c02b2eecd9..9a3e963b02a3 100644
> > --- a/mm/slub.c
> > +++ b/mm/slub.c
> > @@ -677,7 +677,6 @@ static bool freelist_corrupted(struct kmem_cache *s, struct page *page,
> > if ((s->flags & SLAB_CONSISTENCY_CHECKS) &&
> > !check_valid_pointer(s, page, nextfree)) {
> > object_err(s, page, freelist, "Freechain corrupt");
> > - freelist = NULL;
> > slab_fix(s, "Isolate corrupted freechain");
> > return true;
> > }
> > @@ -2184,8 +2183,10 @@ static void deactivate_slab(struct kmem_cache *s, struct page *page,
> > * 'freelist' is already corrupted. So isolate all objects
> > * starting at 'freelist'.
> > */
> > - if (freelist_corrupted(s, page, freelist, nextfree))
> > + if (freelist_corrupted(s, page, freelist, nextfree)) {
> > + freelist = NULL;
>
> This is good to me.
>
> However, this would confuse people when CONFIG_SLUB_DEBUG is not defined.
>
> While reading the source code, people may be curious why to reset freelist when
> CONFIG_SLUB_DEBUG is even not defined.
This is a fair point. To address it, the `freelist = NULL` assignment
should be then moved into the body of freelist_corrupted(). If no
concerns on that, I will soon push a v2 implementing this proposal.
--
Best regards,
Eugeniu Rosca
next prev parent reply other threads:[~2020-08-14 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 12:46 [PATCH] mm: slub: fix conversion of freelist_corrupted() Eugeniu Rosca
2020-08-11 20:49 ` Andrew Morton
2020-08-12 9:06 ` Eugeniu Rosca
2020-08-14 6:57 ` Dongli Zhang
2020-08-14 7:46 ` Eugeniu Rosca [this message]
2020-08-14 19:43 ` Dongli Zhang
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=20200814074644.GA7943@lxhi-065.adit-jv.com \
--to=erosca@de.adit-jv.com \
--cc=akpm@linux-foundation.org \
--cc=dongli.zhang@oracle.com \
--cc=linux-mm@kvack.org \
--cc=roscaeugeniu@gmail.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).