From: Imran Khan <imran.f.khan@oracle.com>
To: vbabka@suse.cz, geert@linux-m68k.org, akpm@linux-foundation.org,
ryabinin.a.a@gmail.com, glider@google.com, andreyknvl@gmail.com,
dvyukov@google.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH v2 0/2] lib, stackdepot: check stackdepot handle before accessing slabs
Date: Thu, 2 Sep 2021 10:01:52 +1000 [thread overview]
Message-ID: <20210902000154.1096484-1-imran.f.khan@oracle.com> (raw)
Original cover letter
---------------------------------------
This RFC patch series addresses suggestion discussed in an earlier
RFC [1]. Since earlier RFC was about SLUB subsystem, and current
changes only involve stackdepot, I am submitting the patches in
a new thread.
The changes of this patch set are as follows:
PATCH-1: Checks validity of a stackdepot handle before proceeding
to access stackdepot slab/objects.
PATCH-2: Adds a helper in stackdepot, to allow users to print
stack entries just by specifying the stackdepot handle.
[1] https://lore.kernel.org/lkml/2772cf56-4183-857f-d070-c54bceb5c8d9@suse.cz/
--------------------------------------
Changes in v2:
- remove WARN messages
- add declaration of stack_depot_print in stackdepot.h
- make current users, which use stack_depot_fetch + stack_trace_print
to print stack entries, use stack_depot_print
Imran Khan (2):
lib, stackdepot: check stackdepot handle before accessing slabs.
lib, stackdepot: Add helper to print stack entries.
include/linux/stackdepot.h | 2 ++
lib/stackdepot.c | 20 ++++++++++++++++++++
mm/kasan/report.c | 15 +++------------
mm/page_owner.c | 13 ++++---------
4 files changed, 29 insertions(+), 21 deletions(-)
--
2.30.2
next reply other threads:[~2021-09-02 0:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 0:01 Imran Khan [this message]
2021-09-02 0:01 ` [RFC PATCH v2 1/2] lib, stackdepot: check stackdepot handle before accessing slabs Imran Khan
2021-09-02 7:53 ` Vlastimil Babka
2021-09-02 0:01 ` [RFC PATCH v2 2/2] lib, stackdepot: Add helper to print stack entries Imran Khan
2021-09-02 7:55 ` Vlastimil Babka
2021-09-03 16:03 ` Alexander Potapenko
2021-09-14 9:01 ` Vlastimil Babka
2021-09-15 3:29 ` imran.f.khan
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=20210902000154.1096484-1-imran.f.khan@oracle.com \
--to=imran.f.khan@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=geert@linux-m68k.org \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryabinin.a.a@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).