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, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@linux.ie,
daniel@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
intel-gfx@lists.freedesktop.org, linux-mm@kvack.org
Subject: [PATCH RESEND 0/3] lib, stackdepot: check stackdepot handle before accessing slabs
Date: Wed, 15 Sep 2021 11:48:03 +1000 [thread overview]
Message-ID: <20210915014806.3206938-1-imran.f.khan@oracle.com> (raw)
This patch series consolidates the changes submitted and reviewed at [1]
and [2].
The patches at [1] and [2] were submitted separarely, but they have some
inter dependency (later patches were created on top of earlier ones).
As both sets are still under review, I have put them in a single
change set here, so that it can be reviewed/included together and also
to avoid automation build failures where git am fails because of absent
parent.
I have included Acked-by (from Vlastimil) and Reviewed-by (from Alexander)
tags obtained so far for these changes and have also addressed last review
comment from Vlastimil [3].
To summarize, the changes in this 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. It also
changes such users to use this new interface.
PATCH-3: Adds a helper in stackdepot, to allow users to print
stack entries into buffers just by specifying the stackdepot handle and
destination buffer. It also changes such users to use this new interface.
[1] https://lore.kernel.org/lkml/20210902000154.1096484-1-imran.f.khan@oracle.com/
[2] https://lore.kernel.org/lkml/20210910141001.1622130-1-imran.f.khan@oracle.com/
[3] https://lore.kernel.org/lkml/ef0aa660-0cb6-dc21-f2ce-368b34f8af3d@suse.cz/
Imran Khan (3):
lib, stackdepot: check stackdepot handle before accessing slabs.
lib, stackdepot: Add helper to print stack entries.
lib, stackdepot: Add helper to print stack entries into buffer.
drivers/gpu/drm/drm_dp_mst_topology.c | 5 +--
drivers/gpu/drm/drm_mm.c | 5 +--
drivers/gpu/drm/i915/i915_vma.c | 5 +--
drivers/gpu/drm/i915/intel_runtime_pm.c | 20 +++--------
include/linux/stackdepot.h | 5 +++
lib/stackdepot.c | 45 +++++++++++++++++++++++++
mm/kasan/report.c | 15 ++-------
mm/page_owner.c | 18 +++-------
8 files changed, 66 insertions(+), 52 deletions(-)
--
2.30.2
next reply other threads:[~2021-09-15 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 1:48 Imran Khan [this message]
2021-09-15 1:48 ` [PATCH RESEND 1/3] lib, stackdepot: check stackdepot handle before accessing slabs Imran Khan
2021-09-15 1:48 ` [PATCH RESEND 2/3] lib, stackdepot: Add helper to print stack entries Imran Khan
2021-09-15 1:48 ` [PATCH RESEND 3/3] lib, stackdepot: Add helper to print stack entries into buffer Imran 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=20210915014806.3206938-1-imran.f.khan@oracle.com \
--to=imran.f.khan@oracle.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=geert@linux-m68k.org \
--cc=glider@google.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=tzimmermann@suse.de \
--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).