From: Kees Cook <keescook@chromium.org>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: [PATCH v2 0/4] pstore: Initial use of cleanup.h
Date: Tue, 5 Dec 2023 10:26:13 -0800 [thread overview]
Message-ID: <20231205175449.work.110-kees@kernel.org> (raw)
Hi,
Mostly as practice for myself, I rewrote a bunch of the error handling
paths in pstore to use the new cleanup.h routines. I'm enjoying this part:
"44 insertions(+), 65 deletions(-)"
It also passes basic testing. :)
-Kees
v2: do not add a global iput macro
v1: https://lore.kernel.org/lkml/20231202211535.work.571-kees@kernel.org/
Kees Cook (4):
pstore: inode: Convert kfree() usage to __free(kfree)
pstore: inode: Convert mutex usage to guard(mutex)
pstore: inode: Use __free(pstore_iput) for inode allocations
pstore: inode: Use cleanup.h for struct pstore_private
fs/pstore/inode.c | 109 +++++++++++++++++++---------------------------
1 file changed, 44 insertions(+), 65 deletions(-)
--
2.34.1
next reply other threads:[~2023-12-05 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 18:26 Kees Cook [this message]
2023-12-05 18:26 ` [PATCH v2 1/4] pstore: inode: Convert kfree() usage to __free(kfree) Kees Cook
2023-12-05 18:26 ` [PATCH v2 2/4] pstore: inode: Convert mutex usage to guard(mutex) Kees Cook
2023-12-05 18:26 ` [PATCH v2 3/4] pstore: inode: Use __free(pstore_iput) for inode allocations Kees Cook
2023-12-05 18:26 ` [PATCH v2 4/4] pstore: inode: Use cleanup.h for struct pstore_private Kees Cook
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=20231205175449.work.110-kees@kernel.org \
--to=keescook@chromium.org \
--cc=gpiccoli@igalia.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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