From: Glenn Washburn <development@efficientek.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>
Cc: Glenn Washburn <development@efficientek.com>,
John Ogness <john.ogness@linutronix.de>,
Petr Mladek <pmladek@suse.com>,
Antonio Borneo <antonio.borneo@foss.st.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/2] GDB VFS utils
Date: Tue, 28 Feb 2023 18:53:33 -0600 [thread overview]
Message-ID: <cover.1677631565.git.development@efficientek.com> (raw)
Hi all,
I've created a couple GDB convenience functions that I found useful when
debugging some VFS issues and figure others might find them useful. For
instance, they are useful in setting conditional breakpoints on VFS
functions where you only care if the dentry path is a certain value. I
took the opportunity to create a new "vfs" python module to give VFS
related utilities a home.
Glenn
Glenn Washburn (2):
scripts/gdb: Create linux/vfs.py for VFS related GDB helpers
scripts/gdb: Add GDB convenience functions $lx_dentry_name() and
$lx_i_dentry()
scripts/gdb/linux/proc.py | 15 +++++-----
scripts/gdb/linux/utils.py | 8 ------
scripts/gdb/linux/vfs.py | 59 ++++++++++++++++++++++++++++++++++++++
scripts/gdb/vmlinux-gdb.py | 1 +
4 files changed, 68 insertions(+), 15 deletions(-)
create mode 100644 scripts/gdb/linux/vfs.py
--
2.30.2
next reply other threads:[~2023-03-01 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 0:53 Glenn Washburn [this message]
2023-03-01 0:53 ` [PATCH 1/2] scripts/gdb: Create linux/vfs.py for VFS related GDB helpers Glenn Washburn
2023-04-12 19:21 ` Andrew Morton
2023-03-01 0:53 ` [PATCH 2/2] scripts/gdb: Add GDB convenience functions $lx_dentry_name() and $lx_i_dentry() Glenn Washburn
2023-04-12 18:02 ` [PATCH 0/2] GDB VFS utils Florian Fainelli
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=cover.1677631565.git.development@efficientek.com \
--to=development@efficientek.com \
--cc=akpm@linux-foundation.org \
--cc=antonio.borneo@foss.st.com \
--cc=jan.kiszka@siemens.com \
--cc=john.ogness@linutronix.de \
--cc=kbingham@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=viro@zeniv.linux.org.uk \
/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).