From: Qian Cai <cai@lca.pw>
To: lijiazi <jqqlijiazi@gmail.com>
Cc: Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
lijiazi <lijiazi@xiaomi.com>,
linux-mm@kvack.org
Subject: Re: [PATCH v2] slub: call BUG if next_object is not valid
Date: Tue, 7 Jan 2020 07:04:52 -0500 [thread overview]
Message-ID: <B17F16A0-735E-4B2C-A5DD-22B03D54AC27@lca.pw> (raw)
In-Reply-To: <1578397918-22017-1-git-send-email-lijiazi@xiaomi.com>
> On Jan 7, 2020, at 6:52 AM, lijiazi <jqqlijiazi@gmail.com> wrote:
>
> If current object's memory is corrupted, there is a high
> probability that next_objext stored in it will be rewritten as an
> illegal value. It's better to check next_object this time than to
> encounter a illegal pointer in next slub alloc like the following:
I still have no answer for the previous question - how was current object’s memory corrupted?
next prev parent reply other threads:[~2020-01-07 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 11:51 lijiazi
2020-01-07 12:04 ` Qian Cai [this message]
2020-01-07 18:00 ` Christopher Lameter
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=B17F16A0-735E-4B2C-A5DD-22B03D54AC27@lca.pw \
--to=cai@lca.pw \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jqqlijiazi@gmail.com \
--cc=lijiazi@xiaomi.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
/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